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

No annotations are provided, so the description carries the full burden. It usefully discloses the return fields (episode code, title, air date, writers, directors, page URL), but says nothing about pagination, the default limit of 10, the max of 50, or result ordering, which matter for a search tool.

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, zero waste: the search dimensions and return payload come first, the sibling routing last. Every clause earns its place.

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 supplies the returned fields, and with no annotations it implies a safe read via 'Find'. It is adequate for a 4-param, all-optional search, though pagination and limit behavior remain unaddressed.

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 75%, and the description complements it by mapping each search mode (title words, season, year first aired) to the corresponding parameters, adding intent beyond raw types. The limit parameter and its default/max are left entirely to the schema, so it is not fully compensating.

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 (Find/Search) and resource (Family Guy episodes) plus the three supported search dimensions. It explicitly separates itself from get_episode, which retrieves a single episode in full, so an agent can choose without opening either 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?

Names the alternative tool (get_episode) and the condition that selects it ('for one episode in full'), giving clear routing context. It does not spell out when-not to use search (e.g., ambiguous titles, no-match behavior), but the alternative is explicit.

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