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

Beyond the readOnlyHint annotation, the description discloses the key behavioral traits: identity is auto-detected from MCP headers, zero arguments are required, the response carries specific profile fields, and no further discovery is needed when a profile exists. It also describes the not-found path, which is behavior not inferable from the schema or 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 but every sentence earns its place: when to call, what it returns, how to consume the result, and what to do on a miss. The WHEN/If found/If not found structure front-loads the most important operational information and is easy to scan.

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?

Although there is no output schema, the description names the returned fields and how they should be mapped into prepare_release_note_context (v1/v2/customModelIds), making the tool callable correctly without further API discovery. It also names the fallback path, so the agent knows what to do in both branches.

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, the schema already states there is nothing to pass, but the description adds the crucial semantic detail that lookup context comes from DEVOPS_ORG_URL/DEVOPS_PROJECT headers and explicitly tells the caller 'you don't pass anything'. This fully removes any guesswork about how inputs are supplied.

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 (check/resolve) and resource (Client Profile for the caller's Azure DevOps org/project) and explains exactly what it returns: currentVersionTag, targetVersionTag, customModelIds, and a diff snapshot. It clearly differentiates itself from siblings like list_release_note_inputs and save_client_profile by positioning it as the pre-flight lookup.

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?

It states an explicit WHEN ('at the START of any release-note / upgrade-impact conversation'), an explicit ordering constraint ('call this BEFORE list_release_note_inputs'), and an explicit fallback ('If not found, fall back to list_release_note_inputs and/or save_client_profile'). An agent is left with no ambiguity about when to choose this tool over alternatives.

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