Listing endpoints from the group

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, fully covering safety and idempotency. The description adds only the permission requirement, which does not contradict annotations. No additional behavioral traits are disclosed.

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 terse at two sentences, front-loading the purpose. However, the first sentence 'Listing endpoints from the group' is redundant with the title. Overall, it is clear and avoids unnecessary detail.

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?

With 17 parameters and an output schema, the description lacks guidance on pagination, filtering, or how to use the many optional parameters. Annotations cover safety and idempotency, but the description leaves agents to infer usage from parameter descriptions alone. Adequate but not comprehensive.

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 description coverage is 100%, so each parameter has a description in the input schema. The tool description adds no additional parameter meaning beyond what is in the schema. Baseline score of 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 'Lists all endpoints included in the specified group', using a specific verb and resource. It distinguishes from sibling tools like 'action1_list_endpoints' (all endpoints) and 'action1_list_endpoint_groups' (list groups). The title also aligns with the purpose.

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 mentions required permission 'Perm: view_endpoints', which provides minimal guidance. It does not explicitly state when to use this tool vs alternatives (e.g., 'action1_list_endpoints'), nor does it mention when not to use it. The permission hint is useful but insufficient.

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