Get today's birthday characters or staff

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

The description discloses key behavioral traits beyond annotations: the 50-result fixed cap with silent omission (no pagination), the difference in returned object shapes, and the lighter fetch nature. This adds substantial context not covered by readOnlyHint/openWorldHint.

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 description is a bit dense, with a long second sentence, but every clause carries essential information. It is front-loaded with the core behavior and then covers caveats, making it efficient despite its length.

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?

The description covers the cap, pagination absence, silent omission, return shape, lighter fetch, and includeDescription behavior. Combined with the output schema and annotations, it is fully sufficient for an agent to use the tool correctly without additional context.

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 already provides 100% coverage, but the description adds valuable semantics: kind determines character-shaped vs staff-shaped objects, and includeDescription is explained with a token-burn warning and alternative. This goes beyond the schema's baseline.

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 lists AniList characters or staff with birthdays today, using a specific verb ('List') and resource. It also distinguishes itself from sibling tools like get_character/get_staff by explicitly noting it is a lighter fetch without filmography.

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?

Explicit guidance is given: use this tool for lightweight birthday lookups, and call get_character/get_staff by ID for full roles/works and bio. It also warns not to interpret missing filmography as 'none', providing clear when-to-use vs alternatives.

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