gsc_alerts

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

No annotations are provided, so the description carries the transparency burden. It clearly says the tool checks for and returns severity-rated alerts, and adds critical behavioral rules (only report data, don't speculate, present visually), which is useful. However, it does not address operational details such as permissions, rate limits, or whether the operation is read-only, so transparency is partial.

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?

The description is front-loaded with the core purpose and uses clear sections. The PRESENTATION block is lengthy and includes agent-facing style instructions that could be viewed as beyond the tool's core description, but every section serves a distinct purpose, so it remains appropriately structured.

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?

Given the lack of output schema and annotations, the description provides a good level of context: alert categories, severity ratings, how to handle data gaps, and presentation expectations. It does not specify exact response fields, but for an alert tool this is reasonably complete.

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%, so the schema already documents all five parameters with descriptions. The tool description adds context about alert types and severity but does not add new parameter-specific meaning; the baseline 3 is appropriate.

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?

The description uses a specific verb 'Check' with a clear resource ('SEO alerts') and enumerates concrete alert types (position drops, CTR collapses, click losses, disappeared pages), making its function clear. However, it does not explicitly distinguish itself from sibling tools like gsc_traffic_drops or gsc_anomalies, so it stops short of full sibling differentiation.

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 description implies when to use the tool—when the user needs a prioritized list of SEO alerts—but it does not state explicit alternatives or exclusions. No guidance on choosing this over gsc_traffic_drops or gsc_anomalies is provided; the 'when to use' is inferred from the purpose rather than stated.

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