list-stream-publishers-vhost-stream

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds no additional behavioral context beyond stating it lists publishers, which aligns with readOnly. Does not disclose pagination, error handling, or other traits.

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?

Single concise sentence of 11 words with no filler. Could be slightly improved by listing parameters or using active voice, but it is efficient and front-loaded.

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 simple read-only list operation with no output schema, the description adequately states the action and scope. However, it omits return format details and does not mention required parameters in the description itself.

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 coverage is 0% with no parameter descriptions. Description does not explain what 'vhost' or 'stream' are or provide format/validation hints. Needed to compensate for missing schema info but fails to do so.

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?

Description clearly states verb 'list', resource 'stream publishers', and scope 'for a stream in a vhost'. It distinguishes from siblings like 'list-stream-publishers' (no scope) and 'list-stream-publishers-vhost' (vhost only) by specifying both vhost and 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?

No guidance on when to use this tool versus siblings like 'list-stream-publishers' or 'list-stream-publishers-vhost'. Does not mention prerequisites, alternatives, or when not to use.

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