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

Annotations already cover the safety profile with readOnlyHint, idempotentHint, and destructiveHint, so the bar for additional behavioral disclosure is lower. The description adds that the data is public and includes source links and credits, but it does not describe error behavior, not-found handling, or any further response structure.

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 short sentences with no wasted words. The identifier mechanism is front-loaded, and the return summary follows immediately, making the definition easy to scan.

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 one-parameter read-only tool, the definition covers how to identify the target and what kind of data will be returned. The lack of an output schema is partially compensated by the return-value hint, though a more explicit statement about not-found or error responses would make it fully complete.

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?

The schema description coverage is 100% and the id parameter is already well documented with a pattern, length constraints, and semantics. The description's 'by UUID or slug' restates the schema rather than adding new meaning, so it stays at the baseline for fully-covered parameters.

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 ('Read'), a specific resource ('published house pizza'), and the accepted identifier forms ('UUID or slug'). This clearly differentiates it from sibling search and list tools, which operate over collections rather than a single identified pizza.

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 intended usage is clear: call this when you already have a UUID or slug and want the public catalog record for one published pizza. It does not explicitly name alternatives like search_pizzas for discovery or read_menu for menu-level reads, but the context is unambiguous enough to guide selection.

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