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

Annotations already declare a safe read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds genuinely non-structured behavior: ranking is by editorial fit and explicitly not paid, and a 'Dutch Fluency item' always ships with independent alternatives. The latter is a useful disclosure although its terminology goes unexplained.

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?

Three tight sentences, front-loaded with the deliverable and the ranking rule, then the routing cue. The final sentence about Dutch Fluency is cryptic and slightly opaque, but it is short and carries a real behavioral fact.

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 and all 6 parameters are undocumented, and with 0 required params an agent could invoke it blind. The description covers the concept and ranking basis but leaves the meaning of kind/type/limit/verified_pro and the 'Dutch Fluency' clause unexplained.

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% across 6 parameters, so the description must compensate and largely does not. Only 'city' and 'goal' are reflected in the text; kind (with its all/provider/tutor enum), type, limit, and verified_pro are left completely undefined.

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 deliverable: a short list of best-fit options for a city and goal, ranked by editorial fit score. It implies a contrast with a broader search tool ('a few recommendations rather than every option') but never names tdd_search, so sibling differentiation is inferred rather than 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?

'Use it when someone wants a few recommendations rather than every option' gives a clear selection condition. No alternative tool is named and no exclusion beyond the search-style case is stated, so it stops short of full routing guidance.

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