get-prompt

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

No annotations provided; description implies a read operation but does not state it is non-destructive. It discloses return type ('Prompt version object') but lacks details on side effects, auth needs, or rate limits.

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?

Highly concise: three sentences plus examples and expected return. Front-loaded with purpose and versioning options, no redundant content.

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?

Covers purpose, usage patterns, and return type. Lacks sibling differentiation and explicit mention of read-only behavior, but sufficient for a simple retrieval tool given no output schema or annotations.

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?

Adds meaning beyond the bare schema: explains that prompt_identifier fetches latest, while tag or version_id select specific versions. Does not specify format or constraints for tag/version_id, but provides functional context.

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 it fetches a prompt, with optional versioning via tag or version_id. It provides examples but does not explicitly differentiate from sibling tools like get-prompt-by-identifier or get-prompt-version, which may overlap.

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?

Examples illustrate common usage patterns but no explicit guidance on when to use this tool versus alternatives (e.g., get-latest-prompt, get-prompt-version). No when-not-to-use or prerequisite conditions.

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