analytics_period_criticality

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

Annotations already provide readOnlyHint=true and openWorldHint=true. Description adds no new behavioral traits (e.g., no side effects, rate limits, or authentication needs). It only restates the tool's focus on criticality, which is already in the name.

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?

Three concise sentences, each serving a distinct purpose: purpose, prerequisite, and usage keywords. No fluff, front-loaded with the core 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?

Missing parameter explanations and output description. No output schema exists, so description should hint at return format. The prerequisite steps are good, but incomplete for a tool with three parameters and no schema documentation.

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 0% with no parameter descriptions. The description does not mention any parameters or their meaning. With low coverage, the description must compensate but completely fails to explain period, paymentMethod, or account semantics.

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?

Description clearly states 'Get criticality breakdown for a statement period' with a specific verb and resource. It distinguishes from siblings by specifying 'inside one statement period', contrasting with the range-criticality sibling tool. Trigger words further aid selection.

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?

Explicit prerequisite: call analytics_periods_list first. Usage context is clear: 'Use for criticality/severity breakdowns inside one statement period.' Does not explicitly mention when not to use or list alternatives, but the sibling context and scope make it adequate.

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