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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful exclusion list ('no secrets, contacts or original files'), but says nothing about result size, pagination behaviour, or what 'through the existing application' implies operationally.

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 no padding, and the read scope is front-loaded before the field restriction. Slightly cryptic phrasing ('through the existing application') is the only waste.

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 no output schema, three fully undocumented parameters, and no explanation of the matrix's dimensions, the description leaves an agent unable to predict either the shape of the response or how to page/filter it. For a read/list tool of this complexity that is a real gap.

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 three parameters (limit, query, offset), so the description carries the full burden and adds nothing — it never mentions filtering or paging. An agent must infer from the names alone what 'query' searches over and how limit/offset behave.

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 verb 'Read' and resource 'location credential matrix' are stated, and the safety scope ('metadata/approved fields only; no secrets, contacts or original files') is clear. However, what the 'matrix' actually contains (locations x credential types vs. requirements vs. status) is never explained, and the near-identical sibling get_location_requirements_matrix is not differentiated.

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?

No when-to-use guidance is given and no alternatives are named. With siblings like get_location_requirements_matrix, get_credential_details, list_credential_types and list_locations, an agent has no basis for choosing this tool over them.

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