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

The description discloses substantial behavior beyond annotations: real conversation creation, sending openers in the user's name, non-guaranteed signup success, always returning signupVerificationRequired=true, no persistent deduplication key, and no concurrent dedupe guarantee. These are critical side-effect and idempotency warnings that annotations only hint at.

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 description is long but every sentence carries essential risk or workflow information. It is front-loaded with the core purpose and login requirement, then layers mode-specific behavior, verification steps, and failure caveats without 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?

For a complex, non-idempotent, side-effect-heavy tool with no output schema, the description covers login requirements, return-field meaning, external form completion, timeout handling, and deduplication behavior. It leaves no critical operational question unanswered.

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?

With 0% schema description coverage, the description compensates well for opener by explaining that omitting it sends a platform-prewritten opener after authorization. arrangementId's meaning is implied through 'accept get_my_dispatch's suggestion' but not explicitly defined, leaving a small semantic 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?

The description opens with a specific verb and resource: accepting the suggestion from get_my_dispatch, and clarifies the two concrete actions MEET and ATTEND. It clearly distinguishes this tool from the sibling decline_dispatch_arrangement by stating what acceptance initiates.

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 explicit routing: use get_signup_activity to verify signup status, list_my_signups to check delivery, and submit_signup only when materials are missing. It also instructs not to auto-resend after unclear results or timeouts, providing strong when-to-use and when-not-to-use guidance.

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