List the prompt groups of the project

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the bar for behavioral disclosure is lowered. The description adds that the output includes visibility and business priority, but does not disclose pagination or date-filtering behavior—though these are covered by the schema. No contradiction with annotations.

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?

Two sentences with zero filler. The first sentence states the purpose and the returned content; the second gives a usage hint. Front-loaded with the most important information.

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?

The description gives a high-level view of the response content (grouping, visibility, priority) but does not explain how the date parameters affect the result or the exact response structure. Since there is no output schema, these gaps are noticeable, though the schema covers the parameters.

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?

All four parameters are fully documented in the schema with 100% coverage, so the description does not need to add parameter meaning. The description does not mention the parameters at all, but the schema already provides adequate semantics, justifying the baseline score of 3.

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?

States the specific verb 'list' and resource 'prompt groups' with additional detail on what is returned (visibility and business priority). Clearly distinguishes from sibling list_prompts, which lists actual prompts rather than groups.

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?

Provides explicit guidance to use a group id to narrow list_prompts, indicating the relationship and a clear alternative. Does not explicitly state when not to use this tool, but the context implies it is for overviews while list_prompts is for individual prompts.

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