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

Annotations only cover the generic safety profile (not read-only, not destructive, not idempotent), so the description carries real weight here and delivers: the activation side effect and its default, the permanence of path_key ('stays taken even after archiving'), and the semantics of level/if_else/defer nodes and repeat behavior. This is context an agent could not infer from the 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?

Front-loaded with the action and its activation behavior, followed by domain context and the read_reference prerequisite. Four dense sentences with little waste, though the middle node-explanation sentence is long and partially duplicates the nodes parameter description.

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 6-parameter tool with nested objects and no output schema, the description covers node structure, activation, prerequisites, and key permanence. It does not mention required permissions or what the call returns, but those are minor omissions given the otherwise thorough treatment.

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%, so the baseline is 3, but the description adds meaning beyond the schema: node-type behavior (paging targets by membership id vs team id, escalate_after waiting), the activate default and its consequence, and the permanent, non-reusable nature of path_key. The extra framing is genuinely useful for constructing valid nodes.

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 ('Create an escalation path with its first revision') and immediately clarifies the domain concept ('A path says who reviews a request the pipeline hands to a person'). This cleanly separates it from update_escalation_path, archive_escalation_path, and the activate_*_revision 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?

Gives an explicit prerequisite: 'Call read_reference (escalation_paths) first.' It does not spell out when to choose create versus update_escalation_path, but the create semantics are unambiguous enough that the gap is small.

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