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

Annotations already declare a non-read-only, non-idempotent, open-world write, and the description adds real context beyond that: an agreement is dispatched to the venue by WhatsApp/email, a quality check runs, a screen ships, and the commission moves to pending then confirmed on first check-in. It stops short of describing failure/rejection behavior or reversibility, so not quite 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?

Three tight sentences, front-loaded with the precondition and outcome; each sentence adds a distinct fact (trigger, downstream flow, claim requirement, commission lifecycle). Slightly long for the payload but nothing is filler.

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 not be explained, and the description covers preconditions and consequences for a 6-required-parameter workflow tool. It leaves open the operational meaning of 'hold the claim' and what happens if the venue declines or the quality check fails, which would be helpful for a workflow step like this.

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% with 9 well-annotated parameters and 4 enums, so the schema fully carries parameter meaning. The description adds no per-parameter detail (e.g., venue_id sourcing, wall_location, agree_channel/contact_email interplay) beyond what the schema already states, 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?

Specific verb (submit) plus resource (venue) gated by a clear precondition (owner/manager agreed in principle), and it describes the resulting downstream flow. This distinguishes it cleanly from siblings like ambassador.venues.claim and ambassador.venues.add, which an agent can differentiate without opening a 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?

States the triggering condition ('once the owner or manager has agreed in principle') and the prerequisite 'You must hold the claim on the venue', which tells the agent what must be true before calling. It does not, however, name the alternative siblings (claim, release, add) or say what to do when the precondition is unmet.

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