get_system_compliance_report

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

No annotations exist, so the description must carry behavioral transparency. It only adds 'Requires PRO tier', which is a constraint, but does not disclose that the tool is read-only, what the response contains, or any side effects. This is insufficient for a tool with 7 parameters.

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 description is extremely concise with one sentence that front-loads the core purpose. Every word is necessary, and there is no extraneous information.

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?

Despite having an output schema, the description is too brief for a tool with 7 parameters and 3 required fields. It fails to explain what 'aggregated compliance report' means, how to use the filters, or the significance of the PRO requirement. The completeness is inadequate for effective agent selection.

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 high (86%), so the baseline is 3. The description adds no additional meaning beyond the schema; it does not explain the purpose or usage of parameters like 'level', 'limit', or 'status'.

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 clearly states 'Get aggregated compliance report for a system', using a specific verb and resource. It distinguishes from sibling 'get_compliance_report' by adding 'aggregated' and 'for a system', making the purpose unambiguous.

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 mentions 'Requires PRO tier' as a prerequisite, but does not provide when to use this tool versus alternatives like 'get_compliance_report'. There is no explicit guidance on filtering or context.

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