employees__get_employee_info

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

Annotations already show readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable extra context: a MCP-server throttle of 1 request per 60 seconds and a caching recommendation, which goes beyond the structured annotations without contradicting them.

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 sentences with no filler: the first states the purpose, the second gives a parameter source and throttling advice. It is well-structured and front-loaded, though slightly more detail on the id parameter could be added without losing conciseness.

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 two-parameter lookup tool, the description covers purpose, one parameter source, and rate limiting. However, it omits how to obtain the employee id and does not describe the return value or error conditions, leaving the description adequate but not 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 description coverage is 0% at the top level, so the description must compensate for parameter meaning. It only explains how to obtain organizationId via organizations__get_organizations, but leaves the employee id parameter source unexplained, providing incomplete semantic guidance.

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 the tool provides employee information by ID, a specific verb and resource. It is easy to distinguish from sibling employee tools focused on couriers or sessions, though no explicit differentiation is made.

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 tells the agent where to get organizationId via organizations__get_organizations and includes a rate-limit note. However, it does not specify when to use this tool over alternative employee info tools or provide exclusions.

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