Create Manufacturer

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

Annotations already indicate the tool is not read-only (readOnlyHint=false), not destructive (destructiveHint=false), and not idempotent (idempotentHint=false). The description adds transparency by advising a dry-run check and specifying the return format (markdown default, JSON if requested). This improves behavioral understanding 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 concise: two short paragraphs with no wasted words. The first sentence states the purpose, the second adds the dry-run instruction, and the last paragraph describes the return format. Every sentence adds value.

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 the schema covers most parameters, the description adds the critical dry-run guidance and return format notes. It does not explain typical usage or prerequisites, but for a creation tool, the context is sufficient. Without an output schema, the description compensates by describing the return format.

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 83%, so the baseline is 3. The description does not provide additional meaning beyond the existing schema descriptions for parameters like name, slug, tags, description, custom_fields, and response_format. The return format note is useful but mentioned only in the context of output, not parameter semantics.

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?

Title 'Create Manufacturer' and description 'Create a new manufacturer in NetBox' clearly state the action and resource. It is clearly differentiated from sibling tools like netbox_list_manufacturers, netbox_get_manufacturer, netbox_update_manufacturer, and netbox_delete_manufacturer.

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 includes an explicit usage guideline: 'Ask before calling if the user wanted a dry-run.' This provides important context for when to use the tool (with user confirmation). However, it does not provide explicit comparisons to sibling tools like update or delete, but the purpose is clear enough.

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