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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description still adds real value by disclosing the 24-hour event-log window (data freshness) and the fixed site target. It does not cover failure modes (e.g. Solid Security not installed) or auth requirements.

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?

Front-loaded with purpose followed by the metric list, then the scope parenthetical and the read-only note; nothing is buried. The 'read-only' clause duplicates readOnlyHint, a small redundancy.

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?

This is a zero-required-param read tool with no output schema, so the description's explicit enumeration of returned fields (version, module count, lockouts, bans, log volume) carries the burden of explaining the response — which is exactly what an agent needs here.

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 site_id param carries an enum with a full URL description, so the schema does the heavy lifting. The description's '(site: demo.royalplugins.com)' merely echoes that value rather than adding new semantics — baseline 3.

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?

Specific verb ('Get a summary') plus the exact resource ('Solid Security state') and an itemized list of the five metrics returned. An agent knows exactly what data comes back. It doesn't differentiate itself from the near-identical sibling gp_get_security_status, so it stops short of a 5.

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 clause 'read-only, runs straight away' implies this is a safe always-call-it first check, but there is no explicit 'use this when…' rule and no mention of when to prefer gp_get_security_status, gp_get_security_stats, or fleet__security_triage instead. Usage is implied rather than stated.

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