Get Contact_group

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

Describes return formats (markdown or JSON) and that JSON includes nested references, adding behavioral context beyond the read-only and idempotent annotations. No mention of error conditions, but annotations cover safety.

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?

Very concise: two sentences for purpose and usage, one for returns. Every sentence adds value, no redundancy, 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?

For a simple get tool with 2 parameters and no output schema, the description covers purpose, usage context, and return format completely. No gaps given the tool's simplicity.

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 coverage is 100%, so baseline is 3. Description adds guidance for the response_format parameter ('Use json when chaining follow-up tool calls'), adding practical semantics beyond the 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?

The description clearly states the action (Get), resource (single contact_group), and identifier (numeric id). It distinguishes itself from the sibling list tool by specifying retrieval of a single object by id.

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?

Explicitly advises use after netbox_list_contact_groups has located the object or when the id is already known, providing clear context. No explicit when-not-to-use or alternatives, but the guidance is sufficient.

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