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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds real value beyond that by scoping returned data ('metadata/approved fields only; no secrets, contacts or original files') and hinting at an authorisation gate, but says nothing about pagination limits, retention, or what a 'week' spans.

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 compact sentences, front-loaded with the verb and resource, with the data-scope caveat in the second. The phrase 'through the existing application' is filler that does not earn 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?

There is no output schema, so the description must carry the return-value burden; it names the exclusion set but not the actual fields, grouping, or period definition ('weekly' = rolling 7 days vs calendar week is unresolved). For a report-retrieval tool with zero documented parameters, this leaves too much for the agent to guess.

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% and none of the three parameters (limit, query, offset) is mentioned or explained in the description. The description does not even imply the report is filterable or paginated, so an agent must open the schema to discover it can narrow results.

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 ('weekly compliance report'), which distinguishes it from the mutating sibling generate_compliance_report. It does not name any sibling explicitly, but the read-vs-generate split is inferable from the verb.

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 statement of when to use this rather than generate_compliance_report, get_compliance_trend, get_compliance_distribution, or the location/site compliance analytics tools. 'Through the existing application' hints at a prerequisite but gives no decision criteria or exclusions.

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