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

Annotations already establish this as a safe, read-only, idempotent operation. The description adds useful context: it is scoped to one employee, requires exactly one identifier, and is a GET endpoint. It does not add richer behavioral details such as pagination behavior or error conditions, but with annotations covering the safety profile this is adequate.

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 two compact sentences plus an endpoint reference. It front-loads the resource and result fields, then gives the key identifier constraint with no wasted text.

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 read-only list tool with no output schema, the description gives enough shape for the return values (degree, institution, major, years, score) and states the identifier constraint. Pagination is only covered by the schema, so a minor gap remains, but the definition is otherwise complete.

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%, so page, limit, user_id, and employee_id are already documented. The description adds a meaningful constraint not enforced by the schema: exactly one of user_id or employee_id must be supplied, which helps an agent invoke the tool 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 clearly identifies the resource: formal education history for one employee, with representative fields (degree, institution, major, years, score). It is specific enough to distinguish from sibling tools like list_family_info or get_employee, though it does not explicitly name alternatives.

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 mostly implied by 'of one employee' and the constraint 'Give exactly one of user_id or employee_id.' However, there is no explicit guidance on when to choose this tool over related employee-information siblings, nor any stated prerequisites or exclusions.

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