v4wordstat_create_report

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

No annotations provided. Description lacks behavioral traits: no mention of side effects, permissions, rate limits, or response handling. Only constraint (10 phrases) and a meta-instruction to call tool_help.

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?

Single sentence with front-loaded purpose. Efficient, but could integrate parameter details instead of deferring to tool_help.

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?

Despite having an output schema, description omits critical details: return value (report ID?), asynchronous behavior, error conditions. Incomplete for a creation tool with 3 parameters.

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 0%. Description adds no parameter meaning beyond names. 'phrases' and 'geo_ids' are obvious, but 'dry_run' is not explained. Defers to tool_help for parameters.

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?

Clearly states it creates a v4 Live Wordstat report via a specific API call, with explicit phrase limit (10). Distinguishes from sibling tools like v4wordstat_get_report and v4wordstat_list_reports.

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 vs alternatives. The name implies creation, and siblings for retrieval exist, but no direct when-to or when-not-to guidance.

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