get_weather_warning_info

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

There are no annotations, so the description bears full responsibility for disclosing behavior. It mentions 'statement and update' but does not explain what these are (e.g., warning statement text, update timestamp). No aggregate behavior like rate limits, pagination, or data freshness is disclosed.

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, concise sentence that front-loads the core action and resource. It is efficient but somewhat cryptic due to the phrase 'with statement and update'. It does not waste words, though it could be clearer without being longer.

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?

While the tool is simple (one optional parameter) and has an output schema, the description lacks necessary context for an agent to decide between this and the summary counterpart. The ambiguous 'statement and update' and absence of any usage guidance make the description incomplete for effective tool selection.

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 only parameter 'lang' is documented in the input schema with a default of 'en', but the description provides zero explanation of it. With 0% schema description coverage, the description should compensate for parameter meaning, but it does not even mention the parameter explicitly.

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 identifies a specific verb ('Get'), resource ('weather warning info'), and geographic scope ('HK'). It adds 'detailed' and 'with statement and update' to convey more than just a basic lookup. However, it does not explicitly distinguish itself from the sibling tool 'get_weather_warning_summary', though 'detailed' implies a contrast.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention selecting between this and 'get_weather_warning_summary' or any other sibling tools, and there are no contextual cues about the appropriate scenario for requesting detailed warnings.

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