Create Site_group

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

Annotations already indicate a non-read-only, non-idempotent write operation. The description adds that it adds a new row and advises dry-run caution, but lacks disclosure of potential side effects like duplicate name/slug errors or permission requirements. 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?

Description is concise with three sentences: clear purpose, usage caution, and return value explanation. Each sentence is necessary and front-loaded with the main action.

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 tool's complexity (7 parameters, nested objects like custom_fields, no output schema), the description adequately explains returns but lacks context about the site_group object's purpose, nesting (parent parameter), or relation to sites. Adequate but could be more helpful.

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 high (86%), so the schema mostly documents parameters. The description adds value only for the response_format parameter by explaining its return format. No additional parameter insights beyond schema.

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?

Description clearly states 'Create a new site_group in NetBox', with a specific verb and resource. Distinguishes from sibling tools like get_site_group, update_site_group, delete_site_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?

The description includes a caution to 'Ask before calling if the user wanted a dry-run', which guides safe usage. However, it does not explicitly explain when to use this tool over alternatives like create_site or when prerequisites are needed (e.g., parent site group existence).

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