v4wordstat_list_reports

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

No annotations provided, and the description adds no behavioral details such as idempotency, authorization needs, or rate limits. It merely restates the listing action without disclosing any behavioral traits.

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 first sentence is concise, but the second sentence instructing to call tool_help is unnecessary given the schema is provided, wasting half the description's space.

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?

Although the tool is simple with one parameter and an output schema exists, the description lacks essential context about behavior and preconditions, making it incomplete for an AI agent given no annotations.

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 description says 'Call tool_help for parameters', adding no meaning to the input schema. The schema has 0% description coverage, and the description fails to compensate, leaving the parameter 'dry_run' unelaborated.

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 'List v4 Live Wordstat reports', using a specific verb and resource. It directly addresses the tool's function and distinguishes it from sibling tools like 'v4wordstat_create_report' and 'v4wordstat_get_report'.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage for listing but lacks context for when not to use it or comparison with other listing tools.

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