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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds value by listing the profile fields returned, which compensates for the absent output schema, but it says nothing about auth requirements, error behavior for a bad/missing id, or whether the record includes archived employees.

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?

One sentence, front-loaded with the core action and scope before the field enumeration. The trailing raw endpoint path 'GET /openapi/v1/employees/basic_info?id=' is implementation noise that doesn't help an agent select or invoke the tool, and the field list is long, but nothing is truly wasted.

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 single-required-param read tool, this is sufficient: annotations carry the safety profile, the schema fully documents the id, and the field enumeration stands in for the missing output schema. An agent has everything needed to call it correctly and know what comes back.

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 coverage is 100% and the single param already has a description and UUID pattern, so the baseline is 3. The description adds provenance ('from jisr_list_employees'), telling the agent where a valid id comes from rather than guessing — a genuine increment over the schema.

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 (fetch a profile) and resource (one employee, by id) and enumerates the returned fields, so the agent knows exactly what this retrieves. It implicitly differentiates from jisr_list_employees by naming it as the id source, though it never contrasts with jisr_get_employee_financial_info or jisr_get_employee_monthly_payables, which cover adjacent employee data.

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 parenthetical '(UUID from jisr_list_employees)' implies the call sequence: list first, then fetch a single record. That's useful routing, but there's no explicit when-to-use/when-not guidance or distinction against the other get_employee_* siblings that also accept an employee id.

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