get_alerts

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

The description discloses caching behavior (30 min expiry and refresh). Since no annotations are provided, this transparency helps the agent understand potential staleness. No destructive side effects are mentioned, which is appropriate for a read operation.

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 concise (4 sentences) with clear structure: purpose, elaboration, caching behavior, and parameter details. Every sentence adds value without repetition.

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 tool's simplicity (1 parameter) and presence of output schema, the description covers all essential aspects: purpose, caching, and parameter format. It is complete enough for correct invocation.

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?

The schema has 0% description coverage, so the description carries the full burden. It provides useful context: 'Two-letter US state code' with examples (CA, NY), which adds meaning beyond the bare schema.

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 clearly states 'Get active weather alerts for a US state', specifying the action and resource. It distinguishes from siblings like get_forecast or clear_old_cache by focusing on alerts.

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 does not provide explicit when-to-use or when-not-to-use guidance compared to siblings. However, the purpose is clear enough that an agent would know to use it for alerts, not forecasts or cache operations.

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