get_prompts_api_v1_prompts

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

No annotations exist, so description carries full burden. Merely stating 'Get Prompts' implies a read operation but does not disclose behavior such as retrieval scope, pagination, sorting, or side effects. Inadequate for a 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?

Extremely concise (2 words) but under-specified. Lacks essential details, making it not earn its place. Contrasts with calibration example for 'Process' which scored 2.

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?

Despite having an output schema and no parameters, the description does not specify what prompts are returned (e.g., all prompts, user-specific, active only). Incomplete for effective tool selection.

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 has 0 parameters with 100% coverage. Baseline is 3. Description adds no additional meaning beyond the empty schema; it does not clarify that no parameters are needed.

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 'Get Prompts' is a tautology of the tool name. It indicates verb and resource but provides no distinction from numerous sibling tools like get_prompt_by_id, get_prompt_list, etc. Vague purpose.

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 usage guidance provided. Agent has no information on when to choose this tool over alternatives like get_prompt_by_command or get_prompt_tags. No context or exclusions.

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