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

With readOnlyHint=true already declaring the safety profile, the description adds genuinely new context: the operation is team-scoped and it discloses the returned payload keys ({escalation, integrations, isPinned, alertRules}) that no output schema provides. It stops short of stating auth scope details or the 404 behavior for a missing/foreign-team id.

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?

Two tight lines, front-loaded with purpose before the endpoint hint, and no filler. The 'Spike: GET /escalations/{escalationId}' fragment is terse to the point of being notation-heavy, but it does add a concrete routing anchor.

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 simple 2-param read tool with annotations covering safety and no output schema, the definition supplies the response shape, the scope, and the id source, which is close to everything an agent needs. It could add the failure mode for an unknown or out-of-team id, but nothing essential is missing.

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 both teamId and escalationId are already fully documented in the schema (including the x-team-id fallback and id provenance). The description adds only the path-level mention of escalationId, so the baseline 3 applies.

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?

States a specific verb and resource ('Get one escalation policy by id') and names the sibling it is not — the singular 'one' clearly distinguishes it from spike_list_escalations. It even enumerates the returned shape, so an agent can tell it apart from the list tool without opening either schema.

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?

Usage is only implied: you call it when you have an escalation id. The 'team-scoped' note gives context, and the schema's escalationId description points at spike_list_escalations as the source of ids, but the description itself states no when/when-not conditions or explicit alternative (e.g. list vs get).

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