obtener_convocante

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

No annotations are provided, so the description carries the full behavioral burden. 'Obtiene los datos' clearly signals a read operation, but it does not explain behavior for missing codes, permissions, or rate limits. This is acceptable for a simple getter, but not deeply transparent.

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 descrciption is a single direct sentence with no padding. It is easy for an agent to parse and the key information is present.

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-identifier tool with one parameter and an output schema, the description covers the essentials. However, it lacks explicit sibling guidance and behavior when the entity is not found, preventing a higher score.

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%, and the description compensates by identifying the parameter as 'código SICP', giving real meaning to the schema title 'Id Convocante'. It does not provide format or examples, but for a single required parameter this is enough to invoke correctly.

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 a specific verb ('obtiene'), a clear resource ('entidad convocante'), and the access criterion ('código SICP'). This distinguishes it from search-oriented siblings, though it does not explicitly mention alternatives like buscar_convocantes.

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?

Usage is implied: call this when you already have a SICP code and need the convocante's data. There are no explicit exclusions or guidance about when to prefer sibling tools such as buscar_convocantes.

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