stat_pivot

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It mentions the HTTP method (GET) and the row/column structure, but does not disclose authentication needs, rate limits, sampling behavior, pagination behavior, or what the response looks like.

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 compact and free of fluff. The API context and docs link are useful, and the row/column explanation is front-loaded. It could be slightly more informative without becoming verbose, but it is well-structured for its length.

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 20-parameter API tool with no annotations and no output schema, the description is too thin. It does not explain when to use this tool, what the response contains, pagination behavior, or authentication requirements. The docs URL helps but is not a substitute for in-description guidance.

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%, so the baseline is 3. The description adds value beyond the schema by explaining that dimensions form rows and pivot_dimensions form columns, which is a relationship not captured in the individual parameter descriptions.

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 identifies the exact API endpoint (GET /stat/v1/data/pivot) and explains the core pivot-table mechanics: rows by dimensions, columns by pivot_dimensions. It is clear about the resource but does not use an explicit verb like 'get' or 'retrieve', and it does not explicitly distinguish itself from sibling stat_* tools beyond the word 'pivot'.

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?

There is no guidance on when to use stat_pivot versus stat_data, stat_drilldown, stat_comparison, or other siblings. The description only states what the tool is, not when it is the right choice or when an alternative would be preferable.

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