List RabbitMQ TopicPermission

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 fully covered by structured data. The description adds nothing beyond that: no statement about what is listed, whether results are scoped to a cluster or namespace, ordering, or pagination behavior.

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?

It is a single short phrase, so there is no verbosity problem, but the brevity is under-specification rather than concision. Nothing is front-loaded because nothing substantive is present.

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 tool with a required cluster identifier, an optional namespace filter, and several closely related RabbitMQ sibling tools, the definition leaves the agent unable to predict what the call returns or how results are scoped. Annotations cover safety and there is no output schema, but the listing semantics remain entirely undocumented.

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% — the required 'cluster' parameter has only a regex pattern and no prose explanation, and the optional 'namespace' relies on a $ref definition. The description does not compensate: it never explains what 'cluster' identifies or that omitting 'namespace' presumably lists across all namespaces.

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 when-to-use guidance at all — no mention of when to prefer this over rabbitmq_topic_permission_get, rabbitmq_permissions_list, or how the optional namespace parameter changes what is returned. The only implied usage is the bare word 'List'.

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