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

Annotations declare writability, open-world behavior and non-idempotency, but the description adds real value beyond that: it names the recipients (panel firm address plus Senior Partner copy), the panel register entry, and the acknowledgement email to the signed-in address. It does not warn that repeat calls create duplicate briefs despite idempotentHint=false, which keeps it from a 5.

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?

Side effects and the usage condition are front-loaded in two efficient sentences with no filler. The enumeration of destinations is slightly dense but every clause carries information an agent needs before invoking a mutation.

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 six-parameter mutation with no output schema, the description covers purpose, recipients, register side effect, and the acknowledgement that serves as implicit confirmation. It omits any statement of what the tool returns on success and any permission or validation requirements, which are the remaining gaps.

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 the schema already documents all six parameters including the 1,200-character summary cap, the security enum, and the forum options. The description restates the same fields without adding format or validation meaning beyond what the schema provides, so the baseline of 3 applies.

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 — 'Sends a new recovery account to the institution's panel counsel as a written brief' — and enumerates the payload (borrower, claim amount, security position, forum, summary, documents). This is clearly distinguishable from siblings such as send_matter_enquiry or book_consultation without opening either schema.

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 when the institution wants to instruct its panel counsel on a new account' gives a clear triggering condition. It does not name an alternative or state when NOT to use it (e.g. for an existing matter, use send_matter_enquiry), so it stops 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.