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

Annotations only declare openWorldHint/destructiveHint, so the description carries the real behavioral load and does: it discloses the response channel and SLA (email within 1 business day with tutor options), the consent precondition, and a privacy constraint (first name only, never a child's full name). These are non-obvious operational and compliance traits an agent must enforce before calling.

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 sentences, front-loaded with the action and routing rule, then prerequisites, then the privacy guardrail. Dense and mostly waste-free, though the confirm/consent sentence is slightly clause-heavy.

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, 3-required open-world submission tool with no output schema, the description covers what is needed: trigger, prerequisites, consent gate, privacy limit, and what the caller gets back (email with tutor options within 1 business day). Nothing an agent needs to call it correctly is 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 description coverage is 83%, so most parameters are already documented and the baseline is 3. The description adds genuine semantic weight: it ties 'collect what the student needs' to the input set and constrains studentFirstName to a first name only, while consent is framed as requiring the user's explicit agreement rather than a flag to set silently.

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 and resource (submit a request for TutorPing to match a student with a tutor) and immediately scopes it against the sibling it replaces. An agent can distinguish this from search_tutors and request_booking without opening any 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?

Explicit triggering condition: use when search_tutors finds no fit or the user prefers to be matched. It also lists the pre-call sequence (collect needs, confirm details, obtain explicit consent) and the alternative, leaving nothing to inference.

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