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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: the pages are 'published' only (scoping), and no account, payment, or recipe inputs are needed, which is non-obvious access information an agent would otherwise have to discover.

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 tight sentences with the core scope front-loaded and the access prerequisites as a supporting clause. Nothing is wasted and no redundancy with the annotations or schema.

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 read-only, optionally filtered list tool with no output schema this covers the essentials of what is returned and the access model. The glaring gap is the undocumented 'query' parameter, which leaves the only input unexplained.

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?

There is one optional 'query' parameter with 0% schema description coverage, and the description never mentions searching or filtering at all. With coverage this low, the description carries the burden of explaining the parameter and it does not, so the agent gets no guidance on what 'query' matches or its syntax.

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 gives a concrete verb (List) and a specific resource (published WAX/WEIGHT candle math pages), so an agent can immediately tell this is a collection-listing operation. It does not explicitly name read_guide as the alternative, so it stops short of full sibling differentiation.

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?

"No recipe inputs, account or payment required" implies this is a no-friction browsing operation, which hints at when it applies. However, it never states when to prefer this over read_guide (e.g., list first, then read a specific page), leaving the sibling relationship to inference.

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