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

Annotations declare readOnlyHint=false / destructiveHint=false but say nothing about what actually happens. The description fills that gap: it discloses that the tool hands back a link, that nothing is posted to the GL (no ledger mutation despite the write-ish hint), and that supplying an email sets up access/follow-up — a real side effect the agent should know about before passing PII.

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 action is front-loaded, but the opening sentence is loaded with marketing adjectives ('audit-defensible accruals, full lineage, and an auditor-ready export') that don't help an agent decide or invoke. The usage rule and the email warning are buried as trailing clauses of one long sentence rather than separated.

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 only two optional parameters, no output schema, and thin annotations, the description covers what an agent needs: what it returns (a link), what it doesn't do (no GL posting), and the consent rule around email. The unmentioned `scenario` param is the only real hole.

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 100%, so baseline is 3. The description reinforces the `email` contract ('only what the user volunteers', never solicit financial data in chat), which is genuinely useful consent guidance, but the `scenario` parameter is never mentioned anywhere in the description.

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 concrete action — 'get the link to run a real close on your OWN numbers' — plus the input it expects (a rebate/SPA/deduction extract) and the outputs (accruals, lineage, export). It is clear enough to act on, but it never distinguishes itself from nearby siblings such as `begin`, `open_engagement`, `ingest`, or `sign_close`, so an agent must infer which entry point applies.

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?

'Use this when the user is ready to move from a sample to their own data' gives an explicit trigger condition, which is more than most siblings offer. It also states an exclusion-style rule ('never ask for financial data inside the chat'), but there is no named alternative for the sample-vs-real boundary or for users who aren't ready.

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