List Elasticsearch roles

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of pagination behavior, default result size, or what happens when a cluster or namespace does not exist.

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 text is a single short phrase with no wasted words, but that brevity comes at the cost of substance — it is under-specified rather than concise. There is no front-loaded explanation of scope, pagination, or required inputs.

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 paginated list tool requiring a cluster identifier and optionally scoped by namespace, the description is far too thin: it omits pagination mechanics and scoping semantics. Annotations cover the read-only safety profile, which prevents a lower score, but an agent would still have to infer most invocation behavior from the schema.

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 0% and there are four parameters, yet the description explains none of them. It does not clarify that 'cluster' is required, that 'limit' caps results at 500 with a default of 100, that 'cursor' is a pagination token, or that 'namespace' scopes the listing.

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?

Tautological: description restates name/title.

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?

There is no explicit guidance on when to use this tool versus alternatives; the plural name weakly implies a collection listing while elasticsearch_role_get fetches a single role, but that inference is left entirely to the agent. No prerequisites, scoping context, or exclusions are mentioned.

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