List categories

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

Discloses pagination behavior (cursor, fetch_all with safety cap) and error handling (verbatim error on 400). No annotations provided, so description carries full burden; these details add transparency beyond basic read operation.

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, no filler. First sentence states purpose and HTTP method; second adds key behavioral details. Front-loaded and 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?

Covers pagination, error handling, and field name reference. No output schema, but response structure is implied. Adequate for a listing tool; could mention that response contains array of categories and pagination data, but still sufficient.

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%, so baseline is 3. Description adds meaningful context: cursor pagination support for 'cursor' parameter, and specific behavior for 'fetch_all' (auto-pagination with 20-page cap). This enhances understanding beyond field descriptions.

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?

Precise verb 'List' and resource 'categories' plus HTTP method. Clearly distinguishes from sibling tools (create, delete, get, update, etc.) which operate on different entities or actions.

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?

States pagination support and error handling advice. While it doesn't explicitly compare to get_category or other list tools, the context is clear: use this when you need to list categories. No exclusions or alternatives needed since siblings are distinct.

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