list_endpoints

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

With no annotations, the description carries the burden. It reveals compact mode and pagination behavior, but does not discuss authentication needs, rate limits, or the exact output structure beyond one-liners vs full JSON.

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?

Three sentences with no filler. Purpose is stated first. Every sentence provides useful information (purpose, compact option, pagination).

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 pagination and filtering, the description covers key aspects. It lacks details on the output format for full mode, but given low complexity and no output schema, it is adequate.

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. The description adds value by explaining that compact mode saves tokens and that pagination is supported with limit/offset, reinforcing defaults and purpose.

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 it lists API endpoints, with specific verb and resource. The name and mention of listing endpoints distinguish it from get_endpoint_details, but it doesn't explicitly differentiate from siblings like search_schema.

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 explains default compact mode for token saving and pagination options, but does not provide explicit guidance on when to use this tool versus alternatives like get_endpoint_details or search_schema.

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