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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's real value is the tier disclosure: the workflow, first step and core rules are free, while the remaining rules are Pro and only 'named by title'. That is a material behavioral fact an agent would otherwise get wrong when summarizing output. It stops short of describing how the returned workflow is formatted or how long it is, which would have pushed it to a 5.

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 trigger condition is placed first, followed by the return contents, then the exemption and the free/Pro split — a sensible information order. The final free-tier sentence is dense but earns its place because it sets expectations about partial output.

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?

With no output schema, the description carries the burden of explaining returns, and it does so by listing the four workflow components plus the caveat that some rules are gated. For a single-optional-parameter read tool the picture is essentially complete; only the shape/format of the returned workflow is left implicit.

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 100% and the single 'task' parameter already carries an example-rich description, so the schema does the work. The prose adds only a loose framing ('what you've been asked to build') and no syntax, formatting, or edge-case guidance beyond it.

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 names a specific verb and resource ('Returns the Product thinking workflow') and enumerates exactly what that workflow contains: target person, underlying problem, success criteria, and what not to build. The word 'Product' plus the trigger 'building a new product, feature or prototype' distinguishes it from the code and copy siblings without the agent needing to open the other tools.

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?

Timing is explicit and front-loaded ('Call this BEFORE building...'), including the precondition that 'what to build and for whom isn't settled'. It also supplies an exclusion path: small changes to an existing product get a two-line check instead, which steers the agent away from this tool for trivial edits.

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