list_endpoints

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

With no annotations, the description carries the full burden for behavioral disclosure. It lacks any mention of side effects, read-only nature, authentication needs, rate limits, or how the output is structured. 'List' implies a read operation but doesn't explicitly guarantee it.

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?

The description is a single, front-loaded sentence. It is concise and avoids any unnecessary content, earning its place without redundancy.

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, the description is adequate but not complete. It lacks explanation of the 'category' parameter, the return format, and any behavioral details. Given no output schema or annotations, the description could have clarified how the endpoint list is structured and how the optional parameter affects results.

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?

The input schema includes an optional 'category' parameter with no description, and the tool description does not explain it. Schema description coverage is 0%, so the description must compensate, but it doesn't. The statement 'List all available' even potentially conflicts with a filtering parameter, leaving the parameter's purpose entirely ambiguous.

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 a specific verb ('List') and resource ('all available Wawp API endpoints'), making it obvious what the tool does. It distinguishes itself from sibling tools like send_local_file or execute_request by focusing on endpoint discovery.

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 offers no guidance on when to use this tool versus alternatives, no exclusions, and no mention of typical scenarios. The only implicit hint is that it lists endpoints, but no explicit 'use this when...' is provided.

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