ntl-extension-operations

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides none. It doesn't indicate whether operations are read-only or destructive, what permissions are needed, what happens during execution, or what the expected outcomes are. The description fails to disclose any behavioral traits beyond the operation names.

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 technically concise - a single sentence listing operation names. However, this conciseness comes at the cost of being severely under-specified. While it's front-loaded with the core instruction ('Run one of the following operations'), the lack of meaningful content makes this efficiency questionable.

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?

The description is completely inadequate for a tool with complex nested operations and no output schema. It doesn't explain what any operation does, what parameters they require, what results to expect, or how this tool relates to sibling tools. For a multi-operation tool with significant complexity, this description provides almost no useful context.

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 provides no parameter information whatsoever. With 0% schema description coverage and 1 parameter (selectSchema) that contains complex nested structures for different operations, the description fails to compensate for the schema's lack of descriptions. It doesn't explain what selectSchema should contain or how to choose between the different operation schemas.

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 merely lists operation names without explaining what the tool actually does. It states 'Run one of the following operations' followed by operation names, which is a tautology that restates the tool's name ('operations') without providing specific verbs or resources. There's no indication of what these operations accomplish in the Netlify context.

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 explain what each operation does, so there's no basis for choosing between them or understanding when this tool should be used instead of sibling tools like ntl-deploy-operations or ntl-team-operations.

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