Get weather warnings

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

No annotations are provided, so description carries full burden. It discloses that warnings are latest and active, and includes AEMET issuance, but does not explicitly state read-only nature, pagination, or behavior when no warnings exist. For a simple 'get' operation, this is adequate but not rich.

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?

Single sentence that is front-loaded with the core action and resource, and includes useful details without digression. Every word earns its place.

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?

Tool has one parameter, no annotations, no output schema, but the description plus schema describe input and output adequately (CAP alerts converted to JSON is in schema). It could mention output format in description, but overall it is sufficiently complete for a simple lookup tool.

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% with detailed description of the 'area' parameter including pattern and example. The main description's note about 'Spanish region or the whole country' adds a tiny bit of context but does not go beyond schema. 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?

States verb 'Get' + resource 'latest active weather warnings (CAP alerts) issued by AEMET for a Spanish region or the whole country', and lists content fields (severity, phenomenon, affected zone, validity). Clearly distinguishes from sibling tools focused on forecasts and observations.

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?

Provides clear context: use for active warnings for a Spanish region or the whole country. Does not explicitly mention alternatives or exclusions, but the scope is well-defined and siblings differ in purpose.

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