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

The description discloses key behavioral traits beyond annotations: the callback is already queued, a broker will reach out regardless of booking, and the book_url is optional. It also discloses the privacy-sensitive side effect of sharing the user's name and email with CHNLSYNC.

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 concise and front-loaded with the core purpose, followed by necessary preconditions and result-handling guidance. Each sentence adds actionable information with no filler or repetition of the schema.

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?

The description is complete for a tool with a visible output schema and minimal annotations: it covers purpose, prerequisites, consent requirements, side effects, and how to handle the result. No critical operational detail is missing for an agent to invoke this correctly.

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%, so the description must compensate for all four parameters. It effectively does so by mapping session_id/session_token to 'session credentials returned by ask_sync_advisor' and contact_name/contact_email to the name and email shared with consent. It does not name the parameters explicitly, but the mapping is clear enough.

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 uses a specific verb and resource: 'Ask a CHNLSYNC human broker to contact the user.' It clearly differentiates this from ask_sync_advisor by stating that it requires the session credentials returned by that sibling, making the workflow relationship explicit.

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 conditions: only call with the user's explicit consent, and only after obtaining credentials from ask_sync_advisor. It also instructs the agent not to present the booking link as required, which prevents a common misuse of the tool.

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