get_assets

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must convey behavioral traits. It mentions pagination (a key behavior) and the max limit for per_page, but does not explicitly state whether the operation is read-only or describe other side effects. Given the listing nature, it's adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short lines, front-loaded with the core purpose, and every sentence provides useful information. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has an output schema, and the description covers the primary behavior and parameters. It lacks guidance on when to use this vs. filter/search variants, but overall it is sufficiently complete for a listing operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, leaving the parameter meanings undefined. The description compensates by explicitly documenting both 'page' and 'per_page', including the max 100 constraint, adding essential meaning beyond the schema's bare types and defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List all assets with pagination', which identifies the specific operation (list) and resource (assets). This distinguishes it from siblings like get_asset_by_id or search_assets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase 'List all assets' - meaning use this to retrieve the full asset list. However, no explicit comparison or guidance is provided for when to use this tool versus alternatives like search_assets or filter_assets.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.