infoprobidad_get_dip

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety and reach profile is covered structurally. The description adds that the tool both downloads AND analyzes the document, which is useful beyond the annotations, but it says nothing about what the 'análisis' produces, whether auth is required, or any rate/availability constraints.

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 well-formed sentence that front-loads the action and resource and ends with the input method. No filler, though it is minimal rather than notably well-structured.

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 should explain what the agent gets back, especially since it claims to 'analizar' the declaration. It never describes the return shape or the nature of the analysis, leaving a real gap for a fetch-and-process tool.

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 coverage is 100% with a single documented parameter, so the schema already carries the parameter meaning. The description's 'por URL o identificador' mirrors the schema's own description without adding syntax, format, or edge-case detail, so baseline 3 applies.

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 pair (descarga y analiza) and a clearly named resource (la Declaración de Intereses y Patrimonio of a public authority) from a named source (InfoProbidad, CGR/CPLT). An agent can tell exactly what it fetches, though no sibling is named or contrasted — there is no obviously adjacent tool to distinguish from anyway.

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 notes the accepted input forms ('por URL o identificador') but gives no when-to-use context, no prerequisites, and no alternatives. Nothing tells the agent under what circumstances this tool is the right choice versus other lookup tools.

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