detalhe_vaga

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

No annotations are provided, so the description carries the burden. 'Detalha' suggests a read-only operation, but it does not mention error behavior, required permissions, or the structure of the returned details. For a simple read, it provides basic clarity but lacks richer behavioral context.

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, front-loaded sentence that conveys the action, object, and key qualifier without any wasted words. It is appropriately sized for the tool's simplicity.

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?

Given the simple one-parameter schema and lack of output schema/annotations, the description is minimal but adequate. However, it does not clarify what 'detalha' returns (e.g., full details vs. summary) or how it differs from 'buscar_vagas' in usage, leaving some gaps for a complete understanding.

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 has one parameter 'id' with no description, but the description states 'pelo ID', clarifying that the integer parameter is the vacancy's identifier. This adds essential meaning beyond the bare schema, though it does not elaborate on format constraints.

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 ('Detalha') and resource ('vaga') and clearly indicates the operation is by ID. This distinguishes it from sibling tools like 'buscar_vagas', which implies searching rather than fetching a single record.

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 implies usage when you have a vacancy ID and need detailed information, but it does not explicitly state when to use this tool versus alternatives like 'buscar_vagas'. There are no exclusions or alternative references.

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