gerent365_get_employee

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

With no annotations, the description carries the full burden. The verb 'Obtiene' implies a read-only operation, which is a positive signal, but the description does not disclose error behavior (e.g., what happens if the ID doesn't exist) or any permission requirements. It adds minimal behavioral context beyond the verb itself.

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, concise sentence with no fluff. It is front-loaded with the action and resource, making it immediately scannable.

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-id tool with one parameter and no output schema, the description is adequately complete: it states what it does and how. It could mention the return shape (e.g., the full employee object), but given the simplicity and the pattern of sibling tools, the gap is minor.

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 100% (the 'id' parameter has a description), so the baseline is 3. The description's 'por su ID' simply restates the parameter's purpose without adding new semantics like format, examples, or constraints, but it does confirm the parameter's role.

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 ('Obtiene' = gets) and resource ('los datos de un empleado') with a clear filter ('por su ID'). It clearly distinguishes from sibling tools like list_employees, which retrieves all employees, and create/update/delete mutations.

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 'por su ID' phrase clearly indicates this tool should be used when you have a specific employee ID and need that employee's data. It provides clear context, though it doesn't explicitly exclude other tools or list alternatives like list_employees for broader queries.

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