cards_browse

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

No annotations are provided, so the description carries the full burden, and it does disclose two concrete behaviors: results are paginated and it returns card briefs (not full cards). It omits the safety profile (read-only), ordering, and any auth or rate-limit notes.

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?

One compact sentence with the classification tag front-loaded, and the pagination/filter facts stated before the return value. No wasted text, though the terseness comes at some cost to clarity.

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 three-parameter browse tool with no output schema and no annotations, the description covers the basics (pagination, shelf filter, brief return type) but leaves the shape of a 'card brief', default page size, and ordering undocumented. Adequate but with real gaps for an agent invoking it cold.

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 description coverage is 0%, so the description must compensate; it touches all three parameters conceptually ('optional shelf filter' for shelf, 'paginated' for limit/offset). However it gives no defaults, no page-size guidance, no shelf identifier format, and no ordering semantics, so it only partially closes the gap.

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 verb 'Browse' plus the name cards_browse make the resource inferable, but the description itself says 'Browse the keeping', which is opaque jargon rather than a clear resource statement. It does signal a list operation distinct from the singular card_get, but never names or differentiates against siblings like cards_stats or card_connections.

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?

'Paginated, optional shelf filter' hints at the listing use case, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as card_get for a single card. The agent must infer that this is for enumerating cards.

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