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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds return-shape detail (public page tutors vs. anonymous matched profiles vs. AI tutors) plus a genuine behavioral obligation not captured anywhere else: 'Always tell the user that an AI tutor is AI.' That policy instruction is real added value, though permission/rate-limit behavior is untouched.

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?

Purpose is front-loaded in the first clause, which is good, but the middle sentence is a dense run-on stacking three different result categories and their sub-fields inside parentheses. The information is useful but would be far easier to parse as separate sentences or a short list.

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?

There is no output schema, so the description correctly carries the burden of explaining what comes back (public tutors, anonymous matched profiles, AI tutors) and it also flags the AI-disclosure obligation. It is close to complete for a read-only search tool, with only pagination/result-count mechanics left unstated.

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 100%, so the schema already documents all four filters with examples, and the baseline is 3. The description echoes the filter dimensions (subject, level, location) and hints at rate via the returned 'rate' field but adds no syntax or semantics beyond what the schema provides.

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?

Names a specific verb and resource (find independent tutors on TutorPing) and scopes it by subject, student level, and location, which distinguishes it from siblings like get_tutor and get_tutor_availability. The audience and subject domains are spelled out, so an agent can recognize the intent without opening the 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?

States explicitly when to use it (students or parents looking for a tutor, listing SAT/ACT, math, science, languages, music) and routes to the alternative when the condition fails: 'If no listed tutor fits, use request_tutor and TutorPing will match one.' That is a concrete when-to-use and when-to-switch rule.

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