tokportal_get_analytics_account

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

Annotations declare readOnlyHint=true and idempotentHint=true, which the description does not contradict. The description adds minimal behavioral context—just 'drilldown' implying detailed/expanded data—but does not specify pagination, sorting, or response size limits. Since annotations already cover the safety profile, the description provides marginal additional value.

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, concise sentence that effectively communicates the action. It is front-loaded with the verb and resource. No wasted words.

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?

With one simple parameter, no output schema, and annotations providing safety cues, the description is minimal. However, given the large number of sibling analytics tools, the description lacks completeness by not clarifying what distinguishes this tool or what output to expect (e.g., 'drilldown' could mean a breakdown by metric or time period). The agent may not know when this tool is relevant.

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 description coverage is 100% (one parameter 'id' with format uuid and a description 'Saved account ID.'). The description does not add any extra meaning beyond the schema, so baseline 3 is appropriate. The description implies the parameter is the account identifier for the drilldown, but no new detail.

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 'Get account analytics drilldown' uses a specific verb ('Get') and resource ('account analytics drilldown'), which clearly indicates the tool retrieves detailed analytics data for an account. However, it does not differentiate from siblings like 'tokportal_get_account_analytics' and 'tokportal_get_analytics_dashboard', which may cover similar or overlapping information, leaving ambiguity about what 'drilldown' specifically means.

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 provides no guidance on when to use this tool versus siblings. With many related analytics tools (e.g., 'tokportal_get_account_analytics', 'tokportal_get_analytics_series', 'tokportal_get_analytics_dashboard'), the agent lacks criteria for selection, such as which one is for aggregate data versus detailed drilldowns.

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