Resolve endpoint group by name (fuzzy)

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds no extra behavioral context beyond 'look up', which is consistent with read-only nature. No contradiction.

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?

One sentence, front-loaded with key verb and resource, no redundant words. Every word adds value.

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 lookup tool with full annotations and a complete schema, the description is mostly sufficient. However, it does not specify what fields are returned (though an output schema exists). Slightly more detail about the result would improve completeness.

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% with descriptions for all parameters. The description adds the matching strategies ('exact-id/exact-name/starts-with/contains') which provides useful context beyond the schema's 'Group name fragment or UUID.'

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 states 'Look up an endpoint group by name or UUID' with specific verb (look up) and resource (endpoint group). The title adds 'fuzzy' and the description mentions matching modes (exact-id/exact-name/starts-with/contains), clearly distinguishing from siblings like list_endpoint_groups and get_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 implies it is for fuzzy lookup but does not explicitly state when to use it versus alternatives like list_endpoint_groups (which lists all groups) or get_group (which gets by ID). No exclusions or when-not-to-use guidance.

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