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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: auto-detection from MCP headers, zero arguments needed, and the exact data returned when a profile exists. There is no contradiction with 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?

The description is dense and front-loaded with the WHEN trigger, and every sentence serves a purpose: timing, preconditions, return data, downstream use, or fallback. The explicit 'WHEN:' marker and sibling references keep the paragraph scannable despite its length.

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?

Even without an output schema, the description tells the agent what to expect (currentVersionTag, targetVersionTag, customModelIds, diff snapshot), how to consume those outputs in the next tool, and what to do on the not-found path. This is sufficient for correct invocation in the broader workflow.

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?

With zero parameters and 100% schema coverage, the baseline is 4, but the description goes further by explaining why no arguments are needed: org/project are auto-detected from DEVOPS_ORG_URL/DEVOPS_PROJECT MCP headers. This is genuinely useful semantic information beyond the empty schema.

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 names a specific verb (resolve) and resource (client profile) and pins down exactly when it is relevant: at the START of any release-note/upgrade-impact conversation. It explicitly distinguishes itself from siblings by referencing list_release_note_inputs, save_client_profile, and prepare_release_note_context, so an agent can route correctly without opening schemas.

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 is explicit about when to call this tool (before list_release_note_inputs), what conditions lead to using its results directly, and which tools to fall back to if no profile exists. This gives the agent a complete decision tree.

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