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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-obvious content behavior: only metadata/approved fields are returned, and secrets, contact data, and original files are excluded — exactly the kind of disclosure annotations cannot carry.

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?

Two tight sentences with the purpose and the exclusion boundary front-loaded; nothing is padded. Minor waste in "through the existing application," which conveys little an agent can act on.

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?

With annotations covering safety and no output schema, the description is serviceable but leaves real gaps: which fields count as "metadata/approved", how query/limit/offset paginate results, and what the authorization failure mode looks like. Adequate as a gate but not complete for correct invocation.

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% across four parameters, so the description must compensate and does not. It never explains that targetId is a UUID identifying the employee whose record is fetched, nor what query/limit/offset do (pagination and filtering semantics are left entirely implicit).

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?

States a specific verb and resource ("Read authorised employee record") plus a firm scope boundary ("Metadata/approved fields only; no secrets, contacts or original files"). However, it never distinguishes itself from near-siblings like list_employees, get_employee_compliance_status, or inspect_employee_readiness, so an agent must infer which employee-scoped read tool to pick.

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?

"through the existing application" implies this is a passthrough read of an already-authorized record, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many employee-related siblings. Usage is only inferable from the scope restriction.

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