get-vhost-topic-permissions

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

The description claims to 'List all topic permissions', but the annotations include 'openWorldHint': true, indicating results may be incomplete or filtered. This contradiction misleads the agent about the tool's 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?

The description is a single, front-loaded sentence that states the tool's purpose without any extraneous words.

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?

Despite simple structure, the description is incomplete due to the contradiction with annotations, and it fails to clarify the parameter's role or note any limitations (e.g., pagination). The openWorldHint contradicts the claim of listing 'all' permissions, making the description unreliable.

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?

The schema has no descriptions and 0% coverage. The description implicitly links the 'name' parameter to a virtual host by stating 'for a given virtual host', adding moderate meaning, but does not explicitly define the parameter or its format.

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 uses a specific verb 'List' and resource 'topic permissions' with scope 'for a given virtual host', clearly distinguishing it from sibling tools like 'list-topic-permissions' (which likely lists all) and 'get-topic-permission' (single permission).

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?

No guidance is provided on when to use this tool over alternatives such as 'list-topic-permissions' or 'list-user-topic-permissions'. The agent must infer based on the description alone.

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