Obtener varios personajes

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the batch nature ('en una sola llamada') and typical id sources, but it does not disclose behavior for missing or invalid ids or ordering. This is adequate given the strong annotations, but not exceptional.

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 short, purposeful sentences. The core action is front-loaded, and the second sentence adds practical usage context without filler.

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 batch read with rich annotations (readOnly, idempotent, openWorld) and an output schema, the description covers the core behavior and typical use cases. Nothing an agent needs to invoke it correctly is missing.

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?

The schema only defines 'ids' as an integer array with 0% description coverage. The description clarifies that these are character ids and can come from an episode's character_ids, adding some meaning beyond the bare schema. However, it does not specify constraints like minimum/maximum count, uniqueness, or handling of duplicate ids.

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 uses the verb 'Devuelve' (returns) with the resource 'varios personajes' and the selection mechanism 'a partir de sus ids', making the core purpose clear. It distinguishes from get_character (single character) and list_characters (all characters) by emphasizing batch retrieval by ids, though it does not name sibling tools explicitly.

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?

It explicitly states when the tool is useful: after a search or when working with an episode's character_ids. This gives clear context for selection, but it does not mention when not to use it or name alternatives like get_character or list_characters.

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