Obtener personaje

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

Annotations already declare the tool read-only, idempotent, and non-destructive, so the description does not need to re-establish safety. It adds a small behavioral detail by promising the complete record returned for an ID, but nothing about auth, limits, or error behavior.

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?

A single concise sentence that states the action and the key input with no filler. It is front-loaded with the verb and resource.

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 get-by-id operation, the description plus annotations and output schema cover what an agent needs: the tool is safe, idempotent, takes one ID, and returns the full character record. There is no missing information necessary to call it.

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 0%, yet the description only restates that the input is a numeric ID, which the schema already encodes through type integer and title 'Character Id'. It does not explain where the ID comes from, its range, or any additional constraints.

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 ('Devuelve') and resource ('la ficha completa de un personaje'), and specifies the input key ('su id numérico'). The singular 'un personaje' distinguishes it from the plural/list siblings such as get_characters and list_characters.

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 implies the tool should be used when a numeric character ID is available and a complete character record is needed. However, it does not explicitly contrast it with list_characters or get_characters, nor state when not to use it.

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