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

Annotations only declare openWorldHint/destructiveHint, so the description carries most of the burden and does well: 1-business-day email reply, an external party (TutorPing) receiving data, and a hard consent precondition. The one real gap is that it doesn't say the call fails without consent, though the schema's const:true hints at it.

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 that are front-loaded with the action, then the trigger, then the turnaround, then the mandatory pre-call steps and privacy rule. No filler; each sentence adds a distinct operating constraint.

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 11-parameter, no-output-schema, write-to-external-service tool, the description supplies the process, the timing expectation, the consent gate, and the privacy constraint. An agent has everything needed to invoke it 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 coverage is 82% (baseline 3), and the description adds genuine meaning: consent is framed as the user's explicit agreement to share the request and contact details, and studentFirstName is constrained to a first name only. It doesn't clarify level/notes/schedule fields beyond the schema, so it sits slightly above baseline rather than at 5.

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+resource ('Submit a request for TutorPing to match a student with a tutor') with the outcome named. It is immediately distinguishable from siblings search_tutors (search) and request_booking (booking a specific tutor).

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 exact trigger condition: when search_tutors finds no fit or the user prefers to be matched, routing the agent from the sibling search tool to this one. It also specifies the pre-call workflow — collect needs, confirm details, obtain explicit consent.

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