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

Annotations already declare this is a write (readOnlyHint=false, destructiveHint=true, idempotentHint=true, openWorldHint=true), so the bar is lower. The description still adds real context beyond them: the act goes through PolicyVera's own consent route and results in the lender seeing the person's insurance progress for the home on the lender's file. It does not say whether the grant can later be withdrawn or who can see the shared data beyond the lender, which is the main gap for a destructive, open-world write.

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 core action is front-loaded, but the first sentence is a colon-chained construction that packs source, consent route, and downstream visibility into one heavy clause. The third sentence earns its place as the when-not rule; the phrasing elsewhere is denser than needed.

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 two-parameter write with no output schema and full annotation coverage, the description covers the source of the ask, the consent semantics, the data-sharing consequence, and the no-call case. What is missing is whether the resulting lender access can be revoked and what a repeat call returns, but nothing essential for deciding to call is absent.

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 100% and the schema already documents both fields, including that lenderPartnerId comes from account.lenderAsk. The description restates that source and says personConfirmed is 'the person's yes,' but adds no format or provenance detail the schema lacks. 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 and resource: records the person's yes to a lender ask surfaced by requirements (account.lenderAsk). It also names the downstream effect (lender sees insurance progress for the home on file). It does not explicitly distinguish itself from nearby siblings such as share_with_lender or tell_lender_new_home, which keeps it short of a 5.

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 a clear trigger (the person has said yes to the pending lender ask returned by requirements) and an explicit when-not: 'Not now is no call: the ask waits on PolicyVera.' No alternative tool is named for the refusal or retraction path, so the routing guidance is clear but not complete.

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