analytics_range_criticality

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

Annotations already declare readOnlyHint=true and openWorldHint=true, which cover safety and variability. The description adds no additional behavioral context (e.g., no mention of rate limits, data freshness). With annotations present, the description adequately confirms the read-only nature but provides no extra depth.

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 very short and front-loaded with the core purpose. However, the 'Trigger words' line is somewhat redundant and consumes space that could be used for parameter clarification.

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 four parameters (two optional), no output schema, and no description of return format or filtering behavior, the description is incomplete. The agent lacks essential context about how the breakdown is structured and how optional filters affect results.

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 input schema has 0% description coverage, and the description does not explain any parameter meaning beyond the implied date range. Optional parameters paymentMethod and account are left entirely undocumented, forcing the agent to guess their purpose.

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 states 'Get criticality breakdown for a date range,' which clearly specifies the action (get), resource (criticality breakdown), and scope (date range). This distinguishes it from sibling tools like analytics_period_criticality (single period) and other range tools focusing on different dimensions.

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 includes explicit usage guidance: 'Use for criticality/severity breakdowns across a custom date range' and provides trigger words. However, it does not explicitly state when not to use this tool versus alternatives like analytics_period_criticality.

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