list-stream-publishers-vhost

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

Annotations already indicate read safety (readOnlyHint) and dynamic output (openWorldHint). The description adds the vhost scope but does not disclose further behavioral aspects like pagination, sorting, or side effects. No contradiction with 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?

A single, clear sentence that is concise and to the point. No unnecessary words, though a bit more detail could be added without sacrificing conciseness.

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 simplicity of the tool (one parameter, no output schema) and existing annotations, the description is adequate but could be improved by noting the return type (list of publishers) and the grouping by vhost.

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?

With 0% schema description coverage, the description should add meaning to the 'vhost' parameter, but it only restates the parameter name. No format, constraints, or examples are provided.

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 (list), resource (stream publishers), and scope (for a given vhost). It effectively distinguishes from siblings like list-stream-publishers (global) and list-stream-publishers-vhost-stream (filtered by stream).

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 provides no guidance on when to use this tool versus the many sibling listing tools. No mention of alternatives, prerequisites, or exclusion criteria.

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