tokportal_create_analytics_report

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

Goes far beyond the annotations by disclosing that the response contains a secret, is never stored in the replay ledger, and that requests with Idempotency-Key are rejected with a specific error before any operation. This is exactly the kind of critical behavioral detail agents need.

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?

Four sentences, each earning its place: purpose, capability, critical warning, and error explanation. No redundancy, front-loaded with the main action.

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 tool with 11 optional parameters and no output schema, the description adequately covers the essential security and error behavior, though it could briefly describe the return value structure beyond just token and URL.

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% and parameter details are left to the schema. The description adds no semantics about individual parameters like 'to', 'from', or 'query', which have self-explanatory names and types in the schema.

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 shareable Analytics v2 web report and returns a token and URL. This specific verb+resource description differentiates it from sibling analytics tools like get_analytics_dashboard or export_analytics_report_html.

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?

Provides clear context for when to use (create a shareable report). The critical 'Do not send Idempotency-Key' warning is strong usage guidance. However, it doesn't explicitly compare to alternative tools or mention when not to use.

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