obtener_datos_profesionales

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

No annotations are provided, so the description carries the full burden. 'Devuelve' implies a read-only fetch, and mentioning 'procedencia y derivaciones' hints at the returned content's traceability, which is useful since there is no output schema. But it discloses nothing about scope, sourcing, or computation conditions, so it is thin for a no-annotation tool.

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 front-loaded sentence with no padding or repetition. It is efficient, though the terseness borders on under-specification given the obscure vocabulary.

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 parameters, no annotations, and no output schema, the description is the only carrier of meaning, and it says only what the return categories are. For a domain-specific fetch in a large sibling set, this is the minimum viable level — enough to form a guess, not enough to invoke confidently.

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 tool takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to disambiguate at the argument level.

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?

It states a verb (Devuelve) and a resource (datos P2 positivos y homopolares), so the operation type is clear. However, the resource is jargon-heavy and opaque — 'datos profesionales' from the name is never explained, and the description does not distinguish this tool from domain siblings like evaluar_cierre_p2 or obtener_secuencia_cero. An agent would struggle to know what 'P2 datos' actually contains.

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?

No when-to-use, no prerequisites, no alternative named. With 70+ siblings, the absence of any routing hint (e.g., when a P2 dataset is needed vs. a sequence-zero query) leaves selection entirely to guesswork.

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