list_assets

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

With no annotations provided, the description discloses critical behaviors: a maximum return of 3 items per request and pagination via the skip parameter. It does not mention the tool's read-only nature or authentication requirements, but the stated constraints add significant transparency.

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?

Two sentences with zero wasted words. The purpose is front-loaded, immediately stating the action and resource, followed by the key constraint and pagination guidance. Every sentence earns its place.

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?

For a simple listing tool with 4 well-described parameters and no output schema, the description covers purpose, key constraints, and pagination. It could briefly mention the return structure (e.g., 'returns asset summaries'), but the existing information is sufficient for an AI agent to use the tool correctly.

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?

Schema coverage is 100% (all parameters described). The description adds narrative context beyond the schema, explaining how 'limit' and 'skip' work together for pagination. While the schema already defines max and default values, the description reinforces the pagination usage pattern.

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 'List assets in a space' provides a specific verb ('list') and resource ('assets'), clearly distinguishing the tool from siblings like get_asset (single asset) and other list tools. Adding the maximum 3 items and pagination notes further clarifies its purpose.

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?

The description states 'Use skip parameter to paginate through results', giving explicit guidance on pagination. While it doesn't explicitly list when not to use it (e.g., for a single asset, use get_asset), the context is clear enough for an AI agent to differentiate from sibling tools.

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