Buscar personajes

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds valuable behavioral detail: it discloses page size, that the response includes total and next-page flags, and that the name filter is a partial match, which are beyond the schema and annotations.

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 succinct sentences in Spanish, front-loaded with purpose and immediately followed by operational details. No filler or repetition of schema/annotation content.

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 explains pagination and name matching, and an output schema exists to document return fields. But it omits explicit routing to sibling tools and valid values for the non-name filters, which are meaningful gaps for a tool with no enum constraints.

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?

With 0% schema description coverage, the description compensates by explaining the name filter's partial matching semantics and the meaning of the page parameter via pagination behavior. However, it does not define accepted values for type, gender, status, or species, leaving an agent to guess at valid filter strings.

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 states a specific verb ('Busca' = searches), resource ('personajes de Rick and Morty'), and method (by name and filters). It clearly differentiates this list/search tool from the sibling get_character/get_characters tools by describing paged results and partial name matching.

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 implies the tool is for searching and filtering characters, and mentions pagination, so an agent can infer when to use it. However, it does not explicitly name alternatives or give a when-not-to-use (e.g., 'use get_character when you have an ID'), leaving the distinction to inference.

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