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

Annotations already cover readOnly and non-destructive behavior. The description adds value beyond those by revealing the external data source, the countywide granularity, and the fact that no sub-county resolution exists. This helps the agent calibrate expectations correctly.

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?

Two sentences: the first establishes resource, location, and source; the second adds an important scope caveat. Every clause contributes useful information with no filler.

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 zero-parameter, read-only tool with an output schema and annotations already enriching safety and behavioral hints, this description is complete. An agent can correctly select and invoke the tool, and understand its limitations.

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 tool has zero parameters, and the schema coverage is 100%, so there is nothing meaningful the description needs to add. This matches the 0-parameter baseline.

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 resource ('outdoor-burning ban status'), location (Harris County, TX), and data source (Texas A&M Forest Service), so an agent can clearly tell it apart from sibling tools like get_alerts or get_current_conditions. The note about Crosby and countywide scope makes the purpose even clearer.

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 explicitly indicates when this tool should be used: for current outdoor-burning ban status in Harris County, TX. It also clearly states the limitation that this is never a Crosby-specific status. It does not name alternative sibling tools, so it stops short of full 'use X instead' guidance.

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