get_prompt

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

Discloses return format as JSON with a messages array and that arguments should be a dict. No annotations exist, so description carries burden; no side effects or error handling mentioned, but adequate for a simple retrieval tool.

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, each adding value: purpose, return format, argument structure. No redundancy, front-loaded with main action.

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 an output schema present, description need not detail return structure further. Covers retrieval and argument usage, but lacks edge case info (e.g., prompt not found). Still complete for typical use.

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 100%, baseline 3. Description adds clarity that arguments should be a dict mapping names to values, which is not explicit in the schema (only object with additionalProperties).

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?

Clearly identifies the verb 'Get', resource 'prompt by name', and mentions optional arguments and return format. Distinguishes from sibling 'list_prompts' which lists prompts rather than retrieving one.

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?

Implied usage is to get a specific prompt, but no explicit guidance on when to use versus alternatives like 'list_prompts', nor any conditions or exclusions.

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