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

With no annotations at all, the description carries the full burden and does substantial work: it discloses the side effect (message sent to the restaurant team), rate limiting, the reply channel, and a one-business-day SLA. It stops short of noting duplicate/idempotency behavior or what happens on failure, so not 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?

Four short sentences, front-loaded with purpose, then the hard precondition, then operational facts. No filler and the most safety-critical constraint is emphasized rather than buried.

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 an 8-parameter mutation tool with no output schema and no annotations, it covers purpose, preconditions, cost (rate limit), and outcome timing. It leaves minor gaps around duplicate submissions and confirmation behavior, but an agent has enough to call it correctly and safely.

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 baseline is 3, but the description adds a genuinely load-bearing rule the schema does not enforce: a phone OR email must be supplied (the schema marks neither as required). That closes a real validation gap the structured fields leave open.

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 (Send) plus the exact resource and its three subtypes (catering / private event / group-dining inquiry), and names the recipient (restaurant team). It is unambiguously distinguishable from every sibling, all of which are read-only get_* info lookups.

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?

Provides an explicit gating condition in caps: 'ONLY call when the person explicitly asked to be contacted and gave their name and phone or email.' That is both a when-to-use rule and an implicit when-not rule (no unsolicited submissions). No sibling alternative exists for this action, so nothing is left to inference.

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