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

With no annotations, the description carries the burden, and it does reveal the operation is a read-only retrieval ('Get') and what the response contains (totals for five compliance categories). It does not discuss permissions or edge cases, but for a zero-parameter read-only summary this is sufficiently transparent.

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?

The entire description is one front-loaded sentence that leads with the operation and immediately specifies all returned categories. Every part is informative and there is no filler.

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?

Given zero parameters and no output schema, this description provides all necessary invocation context: the tool is a no-argument call and the returned summary categories are enumerated. It is complete for an agent to select and call it correctly.

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?

The tool has no parameters, so parameter naming and description constraints do not apply. The baseline of 4 is appropriate because there is nothing the description needs to clarify about arguments.

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 description names a specific verb and resource (get compliance summary) and enumerates the exact totals included, making it clear this is the aggregate dashboard view. This differentiates it from sibling tools that target individual item lists such as get_expiring_docs or list_missing_docs.

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?

The description implies this is the high-level summary rather than a detailed document list, but it never explicitly says when to choose it over get_expiring_docs, list_missing_docs, or search_vendor_docs. An agent must infer usage from the category names; no exclusions or alternative routing are stated.

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