Create Tenant

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds context beyond annotations by stating 'This adds a new row' (confirming a create operation) and describing the return format. No contradiction with 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 with three sentences, front-loading the purpose and return format. 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?

The description covers the return format (markdown or JSON) but does not detail the response structure. Given no output schema, this is adequate but could be more complete, e.g., highlighting that the tool creates a persistent resource.

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 75% (6 of 8 params have descriptions). The description does not add meaning for the uncovered parameters (comments, description) beyond what the schema provides. It mentions response_format indirectly but does not compensate for missing parameter descriptions.

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 tenant in NetBox' and 'This adds a new row to NetBox', providing a specific verb and resource. It distinguishes from sibling tools like netbox_update_tenant and netbox_create_tenant_group.

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?

Includes a caution to ask before calling if the user wants a dry-run, which provides some guidance. However, it does not specify when to use this tool versus alternatives like netbox_update_tenant or netbox_list_tenants.

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