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

Beyond the annotations (which only declare non-readonly, non-destructive, non-idempotent), the description discloses the return artifact (private single-use link, valid 7 days), the downstream sign-in and prefilled-workspace flow, and hard data-handling constraints (never include code excerpts, secrets or personal data; findings carry only paths, line numbers and codes). That is exactly the extra behavioral context the annotations cannot supply.

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?

Front-loaded with the purpose, then the consent requirement, then the data-safety constraint and link-handling instruction, in a sensible priority order. It is a dense paragraph with several clauses, but each sentence carries operational value; no obvious filler.

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 write tool with no output schema, nested object parameters and only half-covered schema descriptions, the description still covers purpose, consent, return value (link + validity), downstream flow and privacy boundaries. Nothing an agent needs in order to call it correctly is missing.

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 coverage is only 50% (only userAgreed is documented), so the description must compensate, and it does: it spells out the payload contents — name, description, confirmed answers and file/line findings from merron_scan_project — which maps to the nested system fields. It stops short of explaining the facts/company/productName fields in detail, so not a 5.

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 opens with a specific verb+resource ('Save this AI system to Merron so the user can build an evidence pack from it') and enumerates exactly what is persisted. It is clearly distinguishable from siblings: merron_scan_project produces the findings this tool consumes, and merron_get_questions supplies the confirmed answers.

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 tells the agent when to invoke it (after the user confirms answers and scan findings exist) and imposes an explicit precondition: 'Ask the user first and tell them what will be saved.' It does not name a when-not case or a competing alternative, so it falls short of a 5.

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