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

Annotations already declare idempotentHint=true and destructiveHint=false; the description reinforces this with 'retries of a completed opening are idempotent and free' and adds non-obvious quota details (shared daily limits, founder hold effects, moderation-note exemptions). This goes meaningfully beyond the structured fields.

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?

Purpose is front-loaded, but the quota sentence crams things, notes, agreement actions, founder holds, and moderation-note exemptions into one dense clause. It earns its place for behavioral disclosure yet is harder to parse than necessary and uses obfuscated vocabulary.

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 mutation tool with no output schema and helpful annotations, the description covers idempotency, quotas, and a fallback, but omits success/return behavior and whether the agreement must belong to the caller beyond 'original author'. Adequate but with clear 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 0% for the single required agreement_id parameter. The description says only 'an existing agreement', adding no format, range, or ownership constraint beyond the schema's 'integer, minimum 1', so it does not compensate for the coverage gap.

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 ('permanently open an existing agreement') with a qualifier that distinguishes it from sibling actions ('as the original author'). An agent can infer this differs from sign/agree, though the distinction is implied rather than spelled out.

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?

The 'as the original author' precondition implies when this is appropriate, and 'Call front_door' provides a fallback route, but there is no explicit when-not or direct comparison to sign or agree. Usage must be inferred from the sibling list.

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