List endpoints

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

No annotations provided, but description fully discloses behavior: it returns endpoints in a specific format, filters by exact tag name, and returns all when no filter. No destructive actions or side effects mentioned, consistent with a read-only listing tool.

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, front-loaded with the output format, no redundant information. Every sentence adds value: output format, filtering, and cross-reference to sibling tools.

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?

Complete for a simple list tool with no output schema. Explains output format, filtering behavior, and how to get more detail via get_endpoint. References list_categories for parameter values.

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?

Parameter 'category' is described as an exact tag name from list_categories, explaining its source and filtering purpose. Schema coverage is 100% and description adds value beyond the schema by specifying the source of valid values.

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?

Description states it lists endpoints with a specific format (METHOD path (operationId) — summary), clearly distinguishing it from get_endpoint (which provides full detail) and list_categories (which lists tags). The verb 'Lists' is specific and the resource is endpoints.

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?

Explicitly says when to use: to list all endpoints or filter by category. Provides alternative: use get_endpoint for full detail. Also references list_categories to get tag names.

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