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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety profile is covered. The description does add a genuine data-scope disclosure — "metadata/approved fields only; no secrets, contacts or original files" — which tells the agent what will not be returned, a useful boundary not encoded anywhere else. It does not describe result shape, pagination behavior, or authorization requirements.

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 operation. Minor waste in "through the existing application," which conveys nothing, but overall tight.

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?

No output schema exists, so the description should explain what the summary returns and whose data it covers; instead it only states what is excluded. Combined with zero parameter documentation, an agent cannot confidently form a call or interpret the response.

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 (limit, query, offset), so the description carries the full burden of explaining them — and it says nothing. The only mitigation is that limit/offset/query are conventional names, but the query's target fields and maxLength=150 constraint are undocumented anywhere.

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 phrase "copliancy summary" (a misspelling of compliance) essentially restates the tool name and title, and "read ... through the existing application" adds no discriminating information. With many nearby compliance-summary siblings (get_compliance_distribution, get_compliance_trend, get_location_compliance_summary, get_weekly_compliance_report, generate_compliance_report), an agent learns nothing about what this summary actually contains or how it differs.

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 to use this tool versus the many compliance-reporting alternatives in the sibling list, and no prerequisites or exclusions. "Through the existing application" is not usage guidance.

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