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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the shape of the result (roles plus episode counts), which implies a read-only lookup, but says nothing about what happens for an unknown name, whether name matching is fuzzy, or any rate limits.

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?

One sentence with zero preamble, front-loading the return content (roles and episode counts). Every clause earns its place and nothing is redundant.

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 must sketch the return value, and it does: roles held and credited episode counts. That is sufficient for a single-parameter lookup tool, though it omits how roles are grouped or ordered in the response.

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 100% and the single parameter 'name' is documented with an example in the schema itself, so the baseline of 3 applies. The description adds no syntax, format, or matching-rule detail beyond what the schema already provides.

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 gives a specific verb and resource: it returns the credits recorded for one person, including roles held and episode counts. Combined with the title naming the person types (writer, director, voice actor), an agent can tell this apart from get_character or get_episode. It stops short of explicitly contrasting itself with those siblings.

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 the phrasing 'the credits this site records for one person' — use it when you have a person name and want their credits. There is no explicit when-not or named alternative (e.g., get_character for character-centric lookups), so the agent must infer routing between this and its siblings.

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