list-prompt-version-tags

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

No annotations provided, so description carries full burden. States it returns array of tag objects with names and IDs, and mentions pagination support. However, doesn't disclose authorization needs, rate limits, or potential side effects (though read-only is implied by 'list').

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?

Three sentences plus example and expected return. No fluff, every sentence adds value. Front-loaded with purpose, followed by usage hint.

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?

With 2 parameters, no output schema, and no annotations, description should cover more. It explains purpose and return type but lacks parameter details and pagination specifics (e.g., offset/cursor). Adequate for a simple list, but could be more thorough.

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%, so description must add meaning. Only mentions prompt_version_id implicitly via 'specific prompt version' and 'pagination support' without explaining the limit parameter or any cursor. Fails to elaborate on format, required vs optional, or pagination mechanics.

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 'Get a list of all tags for a specific prompt version', specifying verb, resource, and scope. Distinguishes from siblings like 'add-prompt-version-tag' (adds) and 'list-prompt-versions' (lists versions, not tags).

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 explicit when/when-not or alternative tools mentioned. Implies use when having a prompt version ID, but doesn't provide guidance on choosing between this and other list tools. Lacks exclusion criteria.

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