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

readOnlyHint=true already tells the agent this is a safe read, and the description adds the conditional behavior that workspace prompts require is_custom and workspace_id. It does not mention pagination, result limits, or error behavior when prompt_id is invalid, so it adds only modest context beyond 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?

Front-loaded with the purpose, then a compact numbered mapping of request values to parameters. Every clause carries information; nothing is redundant.

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?

Output schema exists, so return values need not be described. The description covers both modes and the conditional parameters, though it omits what happens on a missing/invalid prompt_id and whether 'menu' results are paginated.

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 0%, so the description must carry the load, and it explains request's two enum values, the role of prompt_id, is_custom, workspace_id, and prompt_type. It stops short of explaining valid prompt_type values or that is_custom/prompt_id are ignored in 'menu' mode, leaving some gaps.

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 a specific verb and resource: 'Browse the Magento prompt catalog', and the two request modes clarify the surface area. It is clearly distinct from siblings like query_data or execute_action, though it doesn't explicitly say so.

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?

Gives explicit conditions selecting each mode: 'menu' for listing and 'prompt_details' for fetching a body, plus the extra requirement (is_custom=True + workspace_id) for workspace prompts. No when-not guidance or named alternatives, but the routing between modes is unambiguous.

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