get_trial_funnel

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

With no annotations, the description carries the full transparency burden. It discloses the return type (JSON string) and the specific contents ('conversion funnel metrics, timing analysis, and lists of converted/unconverted merchants'), which goes beyond the schema. It does not mention pagination or rate limits, but for a read-only analytics tool this is reasonably complete.

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 concise, uses a clear Args/Returns structure, and every sentence provides necessary information. There is no redundancy or filler.

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?

Given the tool's simple read-only nature, two parameters, and no annotations, the description is complete: it covers the required parameter, optional parameter with format, and outlines the return content. It gives an agent enough information to select and invoke the tool correctly without needing additional context.

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 schema only defines 'app_id' and 'period' as strings with no descriptions or enums (schema coverage 0%). The description compensates fully by specifying app_id as 'App GID or numeric ID (required)' and providing exact allowed values for period ('7d', '30d', '90d', '1y', or 'YYYY-MM-DD:YYYY-MM-DD'), adding essential meaning beyond the raw 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?

The description starts with 'Get trial-to-paid conversion funnel' which is a specific verb and resource, clearly distinguishing it from sibling analytics tools. It explicitly states what the tool does: retrieves trial-to-paid conversion data.

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 implies the use case (trial conversion analysis) but does not provide explicit guidance on when to use this tool versus alternatives like get_churn_analysis or get_retention_cohorts. It gives clear context but no exclusions or alternatives.

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