Listing endpoint groups

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds only the permission requirement, which provides some behavioral context. No contradictions. However, it adds minimal value beyond the 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?

The description is brief but contains some redundancy: 'Listing endpoint groups' and 'Lists existing endpoint groups' repeat the same idea. It could be more concise by merging the first two sentences. However, it is not overly verbose.

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 complexity (9 parameters, output schema exists, many sibling tools), the description covers purpose, filtering/sorting, and permissions. However, it omits explicit mention of pagination behavior, which is important for a list tool with pagination parameters. The output schema likely covers return format, so overall it is moderately complete.

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 the schema already describes all parameters. The description mentions filters and sorting but does not add meaningful detail beyond what the schema provides. Therefore, it does not significantly enhance parameter understanding.

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 is for listing endpoint groups, using the verb 'list' and resource 'endpoint groups'. It mentions filtering and sorting, which aligns with the purpose. However, it does not explicitly distinguish from sibling tools like get_group or list_group_contents, though the context implies it.

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 advises using filters, sorting, and mentions the required permission 'view_endpoints'. It gives basic context on when to use the tool, but does not explicitly state when not to use it or compare to alternatives, such as retrieving a single group or listing group contents.

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