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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, but the description adds substantial behavior beyond them: a mandatory consent gate before data leaves the user's environment, and explicit non-capabilities (no URL fetching, no code execution, no input persistence, no access to private cases). This is exactly the extra context annotations cannot convey.

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?

Three sentences, all front-loaded: purpose and return shape first, then the consent prerequisite, then the prohibitions. Dense and largely waste-free, though the guardrail sentence packs four distinct exclusions into a single long clause, slightly reducing scannability.

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?

With no output schema, the description carries the return contract and does so ('file/line references and follow-up questions'). Safety semantics, consent flow and scope limits are all covered; the only omission is any hint about the 12-file / 8,000-character input caps, which the schema does enforce on its own.

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 description coverage is 50%: sharingConfirmed is documented in the schema, while the files array (path/text/startLine, max 12 items, 8000-char text) has no per-property description. The description reinforces the consent semantics of sharingConfirmed ('obtain the user's agreement', 'user-selected excerpts') but adds nothing about the files payload shape or limits, so baseline 3 is appropriate.

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 ('Find') and precise target artifacts (AI integrations, model calls, disclosure wording, sensitive-use wording) scoped to 'user-selected project excerpts.' The clause 'Returns file/line references and follow-up questions, not a legal classification' explicitly distinguishes it from the sibling merron_screen_ai_act, which is the classification tool.

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 precondition ('First explain that the excerpts will be sent to Merron and obtain the user's agreement') plus hard boundaries on what not to send (secrets, personal customer records, whole repositories, unauthorised files). It does not explicitly state when to prefer this over merron_screen_ai_act, so it falls short of the full when/when-not/alternatives bar.

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