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

Annotations already declare readOnly/idempotent/openWorld, so the bar is low, and the description still adds non-obvious behavior: result ordering ('Most active on Youth4work first') and the returned field set. It does not mention rate limits or total-result caps, but for a read-only search that is minor.

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: scope, filter constraint with examples, then ranking and return fields. Nothing is redundant and the most important constraint (at least one filter) is front-loaded.

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?

With no output schema, the description appropriately names the return fields, and the ordering note covers ranking behavior. The only gap is that pagination semantics and any behavior for zero-match queries are left entirely to the schema, which is acceptable but not exhaustive.

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 the baseline is 3; the description earns above baseline by adding a cross-parameter constraint the schema does not express ('give at least one of' the three filters) plus example values for course and city. It adds little about page, but the schema already handles that.

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 (search) and resource (colleges/universities) plus the domain ('on Youth4work University'), which cleanly separates it from get_college (single lookup) and search_jobs/search_talent. An agent can tell what it does 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?

Explicitly requires at least one of name/course/city and gives concrete value examples for course and city, which is real invocation guidance. It does not, however, mention when to prefer the sibling get_college for a known institution, so the alternative-routing is implied rather than stated.

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