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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description mostly restates this with 'opens nothing by itself'. The genuinely new information is the return content (step-by-step screens/buttons/fields), but it gives no warning that the follow-up browser-driven merge is irreversible and does not say whether the guide is account-specific or generic.

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 first two sentences are front-loaded and useful. The final sentence about Bloomerang's official REST API and MCP availability is irrelevant to invoking this tool and dilutes the core instruction.

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 zero-parameter, no-output-schema guidance tool this is close to complete: it says what is returned and what is not performed. However, it omits any note on guide scope (account-specific vs generic) and spends its closing sentence on unrelated API trivia.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. It could have noted that the guide is generic because no constituent identifiers can be supplied, but that is a minor omission.

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 states a specific resource and outcome: it returns step-by-step instructions (screens, buttons, fields) for merging duplicate constituents in Bloomerang. It usefully corrects the misleading name/title by making clear the tool does not perform the merge itself. It does not distinguish itself from cotlet_app_guide, which could plausibly supply similar guidance.

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 implies usage ('when you need to merge duplicates, get the steps first') and gives a sequencing rule: after reading the steps, perform the merge with the cotlet_browser_* tools. It never states when to prefer this over cotlet_app_guide or what to do if the user's Bloomerang UI differs from the described flow.

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