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

readOnlyHint=true already tells the agent this is a safe read. The description adds one piece of behavioral context beyond that — prices may be missing ("when known") — but says nothing about pagination, default result size, or ordering, which matters for a listing tool.

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, front-loaded with the resource and scope, with no filler. The "(fictional)" qualifier is a minor aside but costs almost nothing.

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 simple two-parameter read tool this covers the basics, but with no output schema the description never indicates what a result contains (name, price, category, availability), and the limit/paging behavior is left entirely to inference. An agent can call it, but cannot predict the response shape.

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 only 50%: query is documented in the schema (case-insensitive on name/description/category), so the description's "optional text filter" is largely redundant, and the limit parameter (default 25, max 100) is never mentioned anywhere. The description does not compensate for the undocumented parameter.

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?

Names the concrete resource (products, services, menu items from Demo Bakery) and its scope (prices when known), which distinguishes it from get_business_info, get_hours, send_inquiry and start_order. The verb is only implied by the name/title rather than stated in the description, so it is clear but not maximally explicit.

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?

Usage is only implied: the agent can infer this is the tool for browsing the catalog or menu. There is no statement of when to prefer it over siblings (e.g., before start_order) and no exclusions or prerequisites are given.

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