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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false). The description adds real behavioural detail: content is sectioned by topic, omitting topic returns the whole playbook, and it contains concrete commission numbers and 'never promise' guidance.

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 'For AGENCIES:' lead is well front-loaded, but the body is a long comma-spliced list of content categories that reads as inventory padding rather than precise routing information.

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 what is returned, and it does list the content sections plus the whole-vs-section default. Adequate for a zero-required-parameter reference tool.

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 100% and the single topic enum is already documented in the schema ('Leave out for the whole playbook'). The description only restates this ('Pass a topic for one section'), so baseline 3 applies.

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 resource (ShearQuery partner-program playbook) and enumerates its contents, so an agent knows this is a static reference/teaching document rather than an action tool. It does not explicitly differentiate itself from the nearby what_shearquery_does tool, which is the only gap.

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?

Gives clear triggering contexts ('teach a new agency', 'whenever an agency asks how to do something or what to say') and a directive to answer from it rather than improvise. No explicit when-not or sibling routing, but the usage condition is unambiguous.

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