netlify-extension-services-updater

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

Annotations declare readOnlyHint=false, which aligns with the description's 'write operations' claim, so no contradiction exists. The description adds minimal behavioral context beyond annotations by specifying this is a selector/dispatcher for two specific operations, but doesn't disclose important traits like whether operations are reversible, have side effects, require specific permissions, or have rate limits. With annotations covering only the read/write aspect, the description provides some but insufficient behavioral context.

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 brief (one sentence) but inefficiently structured. It front-loads the dispatcher concept but wastes space listing operation names without explaining their purposes. The sentence could be more informative by explaining why this dispatcher exists or what 'write operations' entail. While concise, it doesn't maximize information density.

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?

Given this is a mutation tool (write operations) with no output schema and minimal annotations, the description is insufficient. It doesn't explain what the two operations do, their effects, or what they return. The agent must rely entirely on the input schema's parameter names to understand the operations. For a tool that dispatches to potentially destructive operations, more context about behavior and outcomes is needed.

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 description doesn't mention parameters at all, but the input schema has only one parameter (selectSchema) with 0% description coverage. Since this is essentially a dispatcher with a single selector parameter, the lack of parameter explanation in the description is less critical. The description does clarify that users must 'select and run one of the following' operations, which implicitly explains the parameter's purpose. For a single-parameter dispatcher tool, this is reasonably adequate.

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 states 'Select and run one of the following Netlify write operations' which indicates it's a selector/dispatcher tool rather than performing a specific operation itself. However, it's vague about what 'write operations' means and doesn't clearly distinguish this tool from its siblings like 'netlify-extension-services-reader' or other updaters. The description restates the tool name's concept of 'updater' without adding specificity.

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 mentions 'write operations' but provides no guidance on when to use this tool versus its sibling tools. There's no indication of what scenarios require this dispatcher approach versus using individual operation tools directly, nor any mention of prerequisites or constraints. The agent must infer usage from the operation names alone.

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