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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description does add genuinely useful scope information beyond that: only metadata/approved fields are returned and secrets, contacts and original files are excluded, plus an "authorised" access implication. It stops short of describing pagination behavior or what happens on unauthorized access.

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, front-loaded with the verb and resource, and the scope restriction follows immediately. No filler, though the second sentence is terse enough that it reads more like a disclaimer than a specification.

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 zero-required-parameter read tool with annotations covering the safety profile, the definition is serviceable: it establishes the resource and the data classification boundary. However, with no output schema and a non-obvious payload (a "matrix"), the description should say what the matrix contains or how results are paged, neither of which it does.

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% for all three parameters, so the description should compensate, and it says nothing about limit/query/offset. The names are largely self-explanatory and the schema carries defaults and bounds, but there is no hint about what "query" searches over in a requirements matrix, which is the one ambiguous parameter.

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?

"Read ... location requirements matrix" gives a verb and a resource, but "requirements matrix" is never defined, and the description does nothing to separate this from close siblings like get_location_credential_matrix, get_location_compliance_summary, or get_location_record. An agent can tell it is a read of some location-scoped requirements data, but not what the rows or columns represent.

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 statement of when this tool is the right choice versus the many sibling matrix/compliance/credential tools, and no prerequisites (e.g., location id, role) are noted. "Through the existing application" is not usable guidance. The only implicit guidance is the read-only framing.

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