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

Beyond the annotations (write, destructive, open-world), the description discloses a lot of non-obvious behavior: the staged two-call flow bound to an exact payload, token mismatch refusal with nothing sent, 409 on a name that already owns a workspace without a key, workspace refusal when the interface is chat-only, whole-declaration re-validation, and that a submission whose scope does not register cannot be matched. No contradiction with the destructive/openWorld annotations — publishing is indeed an external 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 purpose and trigger are front-loaded, but the body is a single dense wall of text with CAPS emphasis and several passages that restate the schema verbatim (the polling-schedule/interface explanation, dry_run behavior). Those duplicates cost space that could have been trimmed; the re-declare and token guidance is valuable but buried mid-paragraph.

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 12-parameter, nested-object, destructive, open-world tool with no output schema, the description covers the return value (msgid as the only route back to the thread), the dry-run validator output (verdict, failed checks, human-read list, SCOPE reading), and the failure/retry path. Nothing an agent needs in order to call it correctly appears to be missing.

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 the baseline is 3, but the prose adds real semantics the schema does not: identity is claimed by KEY not label, the mandate object's intent shape and that intents are only read from there, and the confirmation_token must match the dry-run payload exactly. Some overlap with schema text (interface/polling schedule) reduces marginal value slightly.

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 gives a concrete verb and resource ('DECLARE something to the Cape exchange — an intent to buy or sell, what they offer, what they need') and enumerates the manifest's constituent parts (identity, wants, offers, interface, delivery contract, boundary, optional mandate). An agent can tell this is the declaration/creation path as distinct from lookup siblings like find_matches or get_deal_flow, even though no sibling is named explicitly.

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?

It states the triggering condition ('Use this when the user wants to DECLARE...'), prescribes a dry_run-first workflow, and covers the re-declare case with the `key` argument, including the 409 failure mode when a key is missing. The only gap is that it never explicitly contrasts with siblings (e.g., join_workspace or reply_to_exchange) or says when NOT to publish.

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