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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing the tool as safe and non-mutating. The description adds credibility by noting these are 'actual templates used across 3,400+ sessions,' which is a useful quality signal. However, it does not disclose output format, limitations, or any behavioral quirks beyond what annotations cover. Given the annotation coverage, the description only needs to add minimal context, and it does.

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 two sentences with no fluff. The first sentence front-loads the core purpose and lists all situations, while the second adds a credibility note. Every word earns its place, and it is appropriately sized for the tool's simple nature.

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?

The tool has an output schema, so the description need not explain return values. It provides the full set of situations, and the annotations handle safety. The only minor gap is that it doesn't mention the engineering-manager audience (though the title does), but that is sufficient. For a read-only, idempotent tool with simple parameters, the description is complete enough for an agent to invoke correctly.

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?

The input schema describes both parameters fully: 'situation' has an enum with inline descriptions for each value, and 'context' has a detailed instruction on word count and perspective. The tool description repeats the situation names but adds no new semantic information beyond the schema. With schema_description_coverage at 100%, the baseline is 3, and the description does not meaningfully exceed that baseline.

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 clearly states the tool provides 'situation-specific 1:1 scripts and templates' and enumerates five specific situations (first-session, underperformance, promotion-to-manager, better-one-on-ones, career-move), each distinct and matching the enum. This makes the tool's purpose unambiguous and easily distinguishable from siblings like get_first_time_manager_guidance or assess_team_lead_readiness, even without naming them.

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 description implies when to use the tool: whenever a user needs a script or template for one of the listed 1:1 situations. It does not explicitly state when not to use it or name alternative tools, but the situation list effectively narrows the context. The phrase 'Situation-specific' signals that selection is based on the exact scenario, and the listed situations align with the enum parameter, giving an agent enough context to choose this tool over generic leadership guidance.

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