Create Cluster

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

Annotations indicate readOnlyHint=false and destructiveHint=false, aligning with creation. The description adds that it creates a new row, and includes a dry-run caution and return format. This provides useful behavioral context beyond annotations.

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 extremely concise: two sentences plus a 'Returns' line. It is front-loaded with the main purpose, and every sentence adds value without redundancy.

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 12 parameters and no output schema, the description covers the core purpose and a usage guideline (dry-run check). However, it omits important context such as required relationships (e.g., cluster type must exist) and does not detail the return structure beyond 'Markdown summary or JSON.' This is adequate but not thorough.

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 does not add any parameter information beyond what the input schema already provides. Schema coverage is 67% (high), so the baseline is 3. The description fails to clarify parameter usage or relationships.

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 states 'Create a new cluster in NetBox' which is a specific verb and resource. It distinguishes from siblings like netbox_update_cluster and netbox_list_clusters by its focus on creation. The dry-run note adds further clarity.

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 instructs 'Ask before calling if the user wanted a dry-run,' which guides when to confirm with the user. It does not explicitly list alternatives (e.g., update or list), but the tool name and sibling list make this context clear.

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