obtener_protesta

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

With no annotations, the description carries the full behavioral burden. 'Obtiene' expresses a read-only retrieval, but it adds no detail about error handling, missing records, authentication, or other behavioral traits beyond the basic fetch operation.

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 single sentence with no filler or redundant restatement. It front-loads the action and resource, then clarifies the input.

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 tool with one required parameter and an output schema, the description is largely complete. It identifies the resource, the action, and the input. It could improve by noting alternatives or specific error behavior, but these are minor for this simplicity level.

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%, so the description must clarify the parameter. 'Dado su id' directly explains that id_protesta is the identifier of the protest/download, which is meaningful even though it closely mirrors the parameter name. It doesn't provide format details, but with one parameter this is sufficient.

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 ('Obtiene') and resource ('datos de una protesta/denuncia'), and explicitly says the input is an id. This clearly distinguishes it from sibling obtener_* tools, which target different resource types.

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 phrase 'dado su id' implies this tool is for fetching a specific protest by id, rather than searching, which distinguishes it from the buscar_* siblings. However, it does not explicitly state when to use this versus the buscar_* tools or mention any exclusions.

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