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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so "read-only, runs straight away" merely repeats structured data rather than adding anything. Beyond the enumerated stat categories, nothing is said about scope, limits, or what an empty result means; with annotations carrying the safety profile, this is adequate but thin.

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?

A single front-loaded sentence with the resource and scope stated first; the parenthetical site note is slightly noisy since site_id is already in the schema, but nothing is bloated or buried.

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 some burden for return values; listing failed logins, blocked IPs, and alerts partially covers that, and annotations handle the safety profile. However, it never clarifies what the statistics look like or how this differs from the near-identical security siblings, which is the main gap for a read-only stats tool in a crowded namespace.

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% with enums on both parameters, so the schema already fully documents `period` and `site_id`. The description only restates "for a time period" and hardcodes the demo site, adding no meaning beyond the schema — 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?

States a specific verb and resource ("Get security statistics") and enumerates the categories returned (failed logins, blocked IPs, alerts), which is more informative than the name alone. It does not, however, differentiate itself from close siblings such as gp_get_failed_logins, gp_get_security_status, or gp_get_dashboard_summary, leaving the agent to guess which one to pick.

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?

There is no statement of when to use this tool versus the many overlapping security siblings, and no prerequisites or exclusions are given. "runs straight away" is a mild cue that no confirmation step is needed, but it is not usage guidance.

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