get_outlier_incident

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description's additional mention of package requirements adds marginal context. No contradiction; description aligns with annotations.

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?

Description is somewhat lengthy with an Args section that largely repeats schema. Front-loaded with main action, but includes redundant information. Could be more concise.

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?

Output schema exists, so return value explanation is not required. Covers basic purpose and feature availability but does not fully detail the query_model structure or its properties beyond schema.

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?

Description minimally explains parameters: incident_id is restated, query_model vaguely described as 'including date range and additional details'. Schema provides description for 'since' but incident_id lacks schema description. With 0% schema coverage in description, it fails to significantly compensate.

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?

Clearly states 'Get Outlier Incident information for a given Incident on its Service', providing specific verb, resource, and context. Distinguishes from sibling tools which are largely other get/list tools for different entities.

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?

Explains that outlier incidents deviate from expected patterns for the same Service and notes feature availability (Event Intelligence package or Digital Operations plan). Provides context for when to use but lacks explicit when-not-to-use or alternative tools.

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