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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real behavior beyond that: the live-vs-recorded duality driven by the month parameter and the prerequisite that the framework be enabled. It does not contradict the annotation. It does not describe output format, but for a read-only report tool this is a solid supplement.

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?

Three well-ordered sentences: what the report contains, how the month parameter alters behavior, and the enablement prerequisite. Front-loaded with the core purpose and free of 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?

With no output schema, the description carries the burden of describing returns, and it does so via the enumerated report contents plus the live/recorded behavior. Prerequisites are covered; only the exact response shape/formatting is left implicit, which is minor for a read-only report.

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 100%, so both parameters are already documented (month as YYYY-MM, framework_key with valid values). The description reinforces the live/recorded distinction and adds the enablement prerequisite for framework_key, but adds only marginal semantics beyond what the schema states, so the baseline 3 fits.

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 and resource ('one compliance framework's report') and enumerates its contents: control-by-control evidence, score, trend. It is clearly distinguishable from plural siblings like get_security_compliance_overview and list_security_compliance_frameworks without opening a schema.

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?

Gives explicit when-to-use guidance: omit month for the live report, supply YYYY-MM to answer an auditor's historical question from the record, and notes the framework must be enabled via list_security_compliance_frameworks. It stops short of an explicit contrast with the similarly-named overview sibling.

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