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

No annotations are provided and the description carries the full burden, yet it discloses nothing about behavior: no read vs write semantics, no permission or auth requirements, no rate limits, no indication of whether the report is generated, cached, or persisted.

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 phrase is short but under-specified rather than concise; the '[security]' tag consumes space without conveying meaning for tool selection. There is no front-loaded action or scope.

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 tool with three required parameters, zero schema descriptions, no annotations, and no output schema, the description is entirely inadequate. Nothing an agent needs to invoke it correctly is present.

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?

All three required parameters (system_id, period, include) have 0% schema description coverage, and the description compensates for none of them. It does not explain the period format (only an example '2026-Q1'), what values the include array accepts, or what system_id refers to.

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 "[security] Transparency report" restates the tool name rather than specifying an action and resource. It gives no verb (generate? fetch? view?) and no sense of what the report covers, so an agent cannot distinguish it from the many compliance siblings.

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 guidance on when to use this tool versus compliance_incident, compliance_oversight, compliance_fairness, or compliance_explain, which appear to overlap heavily with a 'transparency report'. No prerequisites or exclusions are stated.

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