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

Annotations already declare readOnlyHint=true, so the description's restatement of 'Read-only' is redundant. It earns credit by disclosing the payload contents (frequency values, recipients, enabled flag, last/next send times), which is genuinely useful since there is no output schema. It does not cover what happens when no schedule is configured, but the 'whether one is configured' phrasing implies a non-error path.

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?

Lead sentence front-loads the resource and the returned fields, then closes with a short pairing directive. The field enumeration is worth its length because no output schema exists, though the 'Read-only' clause duplicates the annotation.

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 correctly compensates by describing the returned content, and it names both adjacent mutation tools. Complete enough to call correctly; only minor edge behavior (e.g., when unconfigured) is unspecified.

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 coverage is 100% and the single cluster_id parameter carries its own description, including the optional-when-bound-to-a-cluster nuance. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 resource (the cluster's scheduled security report) and enumerates exactly what it returns: configuration status, frequency, recipients, enabled state, last-sent and next-due times. It also distinguishes itself from the mutating siblings by name, so an agent can separate it from set_ and send_ 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?

Explicitly routes the agent: use set_cluster_security_report_schedule to change the schedule and send_cluster_security_report_now to deliver one immediately. Both the alternative and the selecting condition are named, leaving nothing to inference.

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