search_nat_onetoone_mappings

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds no behavioral context beyond what the schema indicates (filtering and pagination), such as pagination behavior, result limits, or client-side filtering specifics. It provides zero new transparency 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?

Single sentence, front-loaded with the core purpose, and no wasted words. The name and description align perfectly.

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 search tool with full schema parameter descriptions and an output schema, the description is adequate. It states the resource and key capabilities. However, it could slightly improve by explicitly distinguishing from sibling NAT search tools, but this is not a significant gap.

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?

All five parameters have descriptions in the schema (100% coverage), so baseline is 3. The description's mention of 'filtering and pagination' adds no meaningful detail beyond schema descriptions; it only summarizes.

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 uses the specific verb 'Search' with the clear resource '1:1 NAT mappings' and mentions 'filtering and pagination'. It effectively distinguishes this tool from sibling NAT search tools like search_nat_port_forwards and search_nat_outbound_mappings by specifying the 'onetoone' resource.

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 implies usage for finding one-to-one NAT mappings but does not explicitly state when to use this tool over alternatives or provide exclusions. The sibling names offer differentiation, but the description itself lacks direct guidance.

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