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

With no annotations, the description carries full burden. It states it returns public reviews with specific fields, but does not disclose ordering, pagination (only limit parameter), or behavior when both slugs are provided. It implies both daycare_slug and program_slug are optional, but does not clarify if one is required or how they interact.

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?

Two sentences, no fluff. The first describes what it returns, the second gives usage context. Every sentence adds value.

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 a simple public read tool with no output schema and minimal parameters, the description is adequate but misses key details like filtering logic (which slug to provide?), ordering, and whether results are paginated beyond the limit parameter.

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 0% (no descriptions in schema). The description mentions 'program or daycare' but does not map daycare_slug and program_slug to these concepts or explain their relationship (e.g., exclusive, both required). It fails to compensate for the lack of schema documentation.

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?

The description clearly states the tool returns public reviews for a program or daycare, listing specific fields (rating, text, reviewer first name, season). It also mentions its use case (surfacing parent sentiment). This distinguishes it from sibling tools like parent_my_reviews (own reviews) and admin tools.

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?

The description provides clear context: 'Used by AIs to surface parent sentiment when recommending a program.' This implies when to use. However, it does not explicitly state when not to use or provide alternatives, though the sibling list suggests many admin/personal tools from which this is distinct.

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