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

Annotations already declare readOnly, idempotent, openWorld. The description adds useful behavioral details: returns category-bucketed examples, includes exact tool+argument shapes, and is drawn from the live catalog. This goes beyond what the annotations provide, though it doesn't discuss edge cases or response formatting.

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 description is long but packed with valuable information. It front-loads example queries and gets to the point quickly. While the first sentence is a run-on, it effectively communicates the tool's purpose and scope. No wasted words, though a slight structure improvement (shorter sentences) would earn a 5.

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?

Given no output schema, the description explains the return content well: category-bucketed questions with tool+argument shapes. It covers inputs, optional parameters, usage scenarios, and expected outputs. For a simple tool with 1 optional param, this is complete and actionable.

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 already has a description for topic, but the tool description adds value by giving concrete examples ('finance', 'pharma') and explicitly stating the behavior when omitted ('full spread', 'cross-category spread'). This clarifies the parameter's semantics beyond the schema.

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 clearly states it is 'the onboarding entry point' for an agent wanting to know what is worth asking, with specific verbs and resource. It lists example queries and distinguishes itself by explaining its output (category-bucketed questions with tool+argument shapes) and guiding toward meta-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?

Explicit guidance is given: 'Call with no arguments for the full spread, or pass topic to focus.' It also says 'Use this FIRST when you do not yet know what Pipeworx can do for you', establishing clear when-to-use. It implies when not to use (once you know, you use other tools) and mentions learning to call meta-tools.

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