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

Annotations already declare readOnlyHint=true, so 'Read-only' in the description is redundant and earns no credit. However, the description adds genuine behavioral value by describing the returned shape (per-framework enabled flag, live score, count of passing controls), which is important since no output schema exists.

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 sentences, front-loaded with the resource and its content before the usage/routing sentence. Dense but largely waste-free; the second sentence is somewhat terse and slightly garbled but conveys its point.

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 zero-param, read-only list tool with no output schema, the description covers what is returned and how to use the result. The only gap is not contrasting it with sibling compliance-listing tools, but nothing essential to correct invocation is missing.

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 takes zero parameters and schema coverage is 100%, so the baseline is 4. The description correctly indicates there is nothing to supply and instead explains that a framework_key is consumed by downstream tools, not passed here.

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+resource (list compliance frameworks) and enumerates the curated set (GDPR, ISO 27001, SOC 2, NIST CSF). It further specifies exactly what each entry contains — enabled state, and when enabled a live score with mapped controls and pass counts — making it easy to distinguish from overview/report 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?

Explicitly routes the agent: the returned framework_key feeds get_security_compliance_framework_report and set_security_compliance_framework. That gives clear downstream context, but it does not differentiate from close siblings like get_security_compliance_overview or get_compliance_reports, so no explicit when-not guidance.

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