nws_station_assist

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

With no annotations, the description carries the full disclosure burden. It reveals that the action is a mutating, AI-mediated operation (create/update pages, tasks, reminders, invites) but says nothing about permissions required, whether actions are confirmed/reversible, non-determinism, latency, or side effects. For a write-capable AI tool with zero annotation coverage this is a meaningful gap.

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 short sentences that lead with the core purpose and then the invocation instruction, with no filler. It is efficient, though extremely sparse for a tool with this much behavioral surface.

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?

No annotations, no output schema, and half the parameters undocumented. For an AI agent that performs writes, the description omits what the call returns, whether the action is synchronous, and how failures or confirmations surface. Too thin for the complexity and risk profile.

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 50%: the 'message' parameter is documented in the schema and reinforced by 'Describe the goal in plain language'. The 'stationId' parameter has no description in either place. The description adds nothing about what stationId accepts or how the plain-language message is interpreted, so it only partially compensates.

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 names a specific mechanism (the NWS station AI) and enumerates the action classes it can take: create/update pages, tasks, reminders, invites. An agent can tell this is an AI-delegation tool rather than a direct-CRUD tool. It does not explicitly contrast with siblings like nws_create_task, so it falls short of a 5.

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?

'Describe the goal in plain language' tells the agent how to invoke it, which implies it is the natural-language catch-all for station actions. However, it gives no explicit when-to-use guidance versus the many specific siblings (nws_create_task, nws_upsert_rows, calendar_create_event), which is the crucial ambiguity for this tool. Usage is implied, not directed.

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