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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the behavior that omitting recipeId returns a catalog while providing it returns a single prompt and HTML starter. This is helpful but does not disclose pagination, error handling, or authentication; the annotations lower the burden, so a 3 is appropriate.

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 two sentences with no filler. The primary action is front-loaded, and the conditional mode is expressed efficiently. Every word earns its place.

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?

For a small get/list tool with no output schema, the description covers the two main invocation modes and clarifies the catalog discovery behavior. However, the version parameter is entirely unexplained, and the return shape of a recipe or catalog entry is not described. It is adequate but has clear gaps.

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 description coverage is 0%, so the description must carry semantic weight. It explains recipeId's role (presence vs. absence changes the result) but says nothing about the version parameter. This partial compensation gives some meaningful guidance but leaves a significant gap.

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 states a specific verb and resource: it lists first-party share/artifacts recipes or retrieves one by recipeId. It clearly distinguishes two modes (catalog discovery vs. single-item retrieval) and stands apart from sibling tools like get_artifact_style and get_page, which target different resources.

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?

The description gives an implicit usage rule: 'Omit recipeId to discover the catalog.' However, it offers no explicit guidance on when to use this tool versus siblings, no exclusions, and no context about prerequisites. The usage is understandable but not fully specified.

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