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

Annotations only declare readOnlyHint and openWorldHint=false; the description goes well beyond them by disclosing the freshness model. It explains that live_verified means a same-day re-check for after-school rows but only a last-extraction status for camps, and that unverified rows may be weeks old. That is exactly the kind of staleness caveat an agent needs before presenting results as 'open'.

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?

The purpose and ordering are front-loaded in the first clause, and the filter list is placed last. The freshness explanation occupies the middle at some length but the content is load-bearing rather than filler; only light tightening is possible.

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 the description does cover the key return semantics: sort order (most recently updated first) and the meaning of the live_verified column. It remains silent on result cardinality/limit behavior for a filterable list endpoint, which is the main remaining gap.

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 5 parameters, so the description must compensate and only partly does: it names region, category, age and vertical as optional filters but gives no value formats, and never mentions limit (max 25) or the result-count default. Four of five parameters get at least a category label, which is more than nothing but not full compensation.

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 resource and scope: 'Programs currently OPEN for registration, most recently updated first.' An agent can tell this is a browsing/status-listing tool rather than a keyword search or detail fetch. It does not, however, name or contrast any sibling (e.g. search_programs), so sibling differentiation is left to inference.

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?

Usage is implied by 'currently OPEN for registration' plus 'Optional filters: region, category, age, vertical', which tells the agent when the tool is applicable. There is no explicit when-not guidance, no mention of the alternative (search_programs for text queries, get_program_details for a single result), and no prerequisites stated.

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