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

Annotations carry only a title, so the description bears the full disclosure burden - and it delivers the important part: accepting issues a receipt and Seed and mints a slot/mission for post-origin entries, and constitutional entries are gated by governance. It still omits reversibility, failure behavior, and the meaning of the optional idempotency key.

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?

A single front-loaded sentence plus a parenthetical clause; every element carries information and nothing is padded. The parenthetical is jargon-dense ('receipt + Seed; slot/mission minted for post-origin entries') and assumes domain vocabulary, but it is not wasteful.

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?

An output schema exists, so return values need no explanation, and the description covers actor, side effects, and the governance exception for a mutation tool. Gaps are minor: idempotency semantics and what distinguishes post-origin from constitutional entries are left unstated.

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%, so api_key, agreement_id, and idempotency_key are already documented in structured form, including the owner-auth constraint on api_key. The description adds no syntax, format, or constraint detail beyond that, so the baseline 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 ('Opportunity owner accepts an entry') and scopes it to the opportunity owner, which separates it from entry.reject and entry.withdraw by implication. It does not explicitly name those siblings, so an agent must infer the routing rather than being told.

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 description gives one real conditional exclusion - constitutional entries must go through the governance gate rather than being accepted here - which usefully points toward the govern.* family. However, it never says when to accept versus reject or withdraw an entry, so the primary usage decision is left implicit.

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