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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is known. The description adds genuinely non-obvious context: results are restricted to authorised (permission-filtered) employees and to metadata/approved fields, explicitly excluding secrets, contacts, and original files. It doesn't mention pagination or result ordering, which keeps it from a 5.

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 short sentences with the core action first and the data-scope caveat second; nothing is padded. It is arguably over-compressed given the undocumented parameters, but every sentence present earns its place.

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 0% schema description coverage and no output schema, the definition carries full burden for explaining the four parameters and the return shape, and it does neither. An agent cannot tell from the description what 'query' searches or what fields come back beyond 'metadata/approved fields'.

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% — none of the four parameters (limit, offset, query, targetId) carry any documentation. The description only indirectly implies targetId is a location identifier; it says nothing about what 'query' filters on (name? email?), how paging behaves, or the max page size.

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 ('Read') and resource ('location employees'), and the phrase 'location' plus the required targetId makes the scope concrete. It does not, however, differentiate itself from siblings like list_employees or get_employee_record, so an agent must infer the boundary.

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?

There is no guidance on when to use this versus list_employees (which likely returns the same entity without location scoping) or get_employee_record. The phrase 'through the existing application' is vague and does not identify a selection condition or any alternative.

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