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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the function (returns alerts near coords) but does not mention read-only nature, rate limits, response format, error handling, or coordinate format. This is a significant gap for an agent to call it correctly without guessing.

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 a single, front-loaded sentence that states the core function immediately. There is no filler or redundancy. Every word earns its place, making it highly concise and efficient for an agent to parse.

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?

For a simple tool with one parameter and an output schema, the description is adequate but not fully complete. It lacks specification of coordinate format and any usage notes. Given the output schema exists, return format is covered, but the missing parameter format and lack of behavioral context leave some gaps for an agent to infer.

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 input schema has one parameter 'q' with no description and 0% schema coverage. The description adds meaning by stating 'near coords', indicating that 'q' represents coordinates. This is helpful but incomplete—it does not specify the expected format (e.g., lat,lon as decimal degrees). It partially compensates for the schema gap.

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 the tool provides active US NWS weather alerts near given coordinates. It uses a specific verb (get/retrieve implied), names the resource (weather alerts), and scopes to US NWS and proximity. It distinguishes from siblings like 'weather' (current conditions) and 'marineweather' by focusing on alerts, making its purpose unambiguous.

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 usage when an agent needs weather alerts for a location, but it does not explicitly compare to alternatives like 'weather' or 'marineweather'. There is no mention of when not to use it or which sibling to prefer. The guidance is only implied through the purpose statement, not explicit.

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