nws_create_chart

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

No annotations are provided, so the description carries the full behavioral burden for a mutating tool. It does not state whether creation is idempotent, whether it requires page-edit permissions, how it interacts with existing blocks, or what happens on failure. 'From a data source payload' is the only behavioral hint, and it is not elaborated.

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?

A single front-loaded sentence with no filler, and the core action is stated first. It is concise, though the brevity is partly under-specification rather than disciplined editing.

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 6-parameter mutation tool with no annotations, no output schema, and 17% schema coverage, the description is far too thin. An agent cannot determine valid chart types, required source payload shape, or placement behavior before invoking it.

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 description coverage is only 17% — just the 'source' parameter is documented. Six parameters exist (pageId, chartType, source, axis, parentId, sortOrder), and the description explains none of them, leaving chartType values, axis structure, and placement semantics (parentId/sortOrder) undocumented in both places.

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 gives a specific verb and resource: 'Create a chart block on an NWS page from a data source payload.' That is clearer than a tautology and identifies both the artifact (chart block) and its parent (NWS page). It does not, however, distinguish itself from siblings like nws_search_blocks or nws_apply_template_blocks, which also operate on NWS page blocks.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites such as needing an existing page or a populated data source. The agent must infer all routing decisions from the name alone.

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