buscar_acta_cursada_docente

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

No annotations are provided, so the description must carry the full burden. It only says 'Busca' (search), which implies a read-only operation, but it does not explicitly state side effects, return behavior, error handling, or authentication requirements. There is no mention of what happens when the acta is not found or how results are presented.

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 that is efficient and directly states the core functionality. Every word contributes to the meaning, with no unnecessary detail or fluff.

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?

Although the tool has only one parameter and an output schema, the description lacks workflow context and does not clarify its role among sibling tools. It mentions 'dentro de Reporte de Actas' but does not explain prerequisites, when to use it, or how it relates to 'detalle_acta_cursada_docente' and other related tools. This incompleteness could lead to incorrect tool selection.

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 schema description coverage is 0%, and the description adds only 'por número' (by number), which is redundant with the parameter name 'numero_acta.' It does not explain the expected format, constraints, or how the number should be provided (e.g., string length, leading zeros). The parameter type is already 'string' in the schema, but the description offers no additional meaning.

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 clearly states it searches for a course acta by number ('Busca un acta de cursada por número'), pinpointing the specific verb and resource. It also adds the context 'dentro de Reporte de Actas.' However, it doesn't explicitly differentiate this from sibling tools like 'detalle_acta_cursada_docente,' which may also involve searching by number.

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 description provides no guidance on when to use this tool versus alternatives. The phrase 'dentro de Reporte de Actas' hints at a context but does not explain when to choose this tool over siblings like 'detalle_acta_cursada_docente' or 'resolver_cursada_docente'.

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