list_prompts

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention authorization requirements, side effects, or what happens if the property does not exist. The description is too brief to provide sufficient transparency.

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?

The description is a single sentence, concise but awkwardly phrased ('prompts a property tracks'). It conveys the essential information without fluff, though clarity could be improved.

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?

No output schema exists, so the description should explain the return format. It mentions 'engines, last run and runs-in-range' but does not specify structure, pagination, or error handling. This is incomplete for a list tool.

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?

There are zero defined parameters in the schema, but description mentions filtering by engine (ChatGPT, Claude, Gemini, Perplexity). However, it does not specify the parameter key or format for this filter. The schema allows additional properties, leaving ambiguity.

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 the tool lists prompts tracked by a property, with details like engines, last run, and runs-in-range. It distinguishes from sibling tools by focusing on prompts, which is unique among the list tools.

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 guidance on when to use this tool versus alternatives. The description implies it is for listing prompts with optional engine filtering, but does not state when not to use or provide any contextual hints.

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