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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Fetch' is consistent with those. The description adds no behavioral detail beyond the annotations, such as error/not-found behavior or required permissions, so it is adequate but not enriching.

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 one short, front-loaded sentence with no filler. Every word adds meaning: it names the action, scope, and lookup key.

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 read-only single-resource lookup with one well-documented parameter and safety annotations, the description is sufficient to invoke the tool correctly. It does not describe the return shape or 404 behavior, but 'Fetch' strongly implies the rule is returned, and the tool's simplicity keeps this gap minor.

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 100% and the only parameter id is described as 'Escalation rule id.' The description's 'by id' reinforces the schema but does not add semantic detail like id format, where to obtain it, or constraints. Baseline 3 is appropriate because the schema carries the meaning.

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 a specific verb (Fetch), a resource (escalation rule), and a lookup criterion (by id). It clearly describes the tool's function and the singular 'single' distinguishes it from list_escalation_rules, though it does not explicitly differentiate from other get_* siblings.

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 intended use is implied: call this when you need one escalation rule and have its id. However, there is no explicit guidance about alternatives (e.g., use list_escalation_rules to discover ids or create/update/delete for mutations), leaving selection partly to inference.

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