Get Fhrp_group_assignment

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value by specifying the output format (Markdown or JSON) and noting that JSON includes nested references. This is useful but could be enhanced with error handling or field details.

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 with three sentences: purpose, usage guideline, and return format. Every sentence serves a clear purpose without redundancy, making it easy for agents to parse quickly.

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 operation with full schema and annotation coverage, the description covers all essential aspects: what it does, when to use it, and what it returns. No gaps remain, as the agent can infer error handling from standard NetBox behavior.

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 parameters are already well-documented. The description does not add significant new meaning beyond the schema descriptions, though it reinforces the output format for response_format. Baseline 3 is appropriate.

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 tool retrieves a single fhrp_group_assignment by numeric ID, using the verb 'get' and specifying the resource. It distinguishes from sibling list, create, and update tools by emphasizing single object retrieval and the prerequisite of having the 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 instructs to use after netbox_list_fhrp_group_assignments or when the ID is already known, providing clear context for when to employ this tool versus alternatives. This prevents misuse when a list or search is needed.

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