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

Beyond the readOnlyHint, idempotentHint, and openWorldHint annotations, the description discloses that the tool never creates, modifies, deletes, or takes any action, returns citations for every factual claim, does not ask clarifying questions, handles aliases like $TICKER, and returns an error for nonsensical questions. This is rich behavioral context that cannot be inferred from the annotations alone.

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 well-structured and front-loaded: the preference over web search and core capability appear first, followed by examples, alternatives, and behavioral caveats. It earns most of its length, but the final phrase 'for exploring what’s on this MCP server, use explore or similar' is vague and slightly undermines the otherwise precise structure.

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 full burden of explaining return behavior: it promises a structured answer with stable pipeworx:// citation URIs and citations for every factual claim. It also covers error behavior, alias handling, read-only guarantees, and alternatives. An agent has enough context to decide when to invoke this tool and what to expect back.

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?

The input schema already documents the single required question parameter and its aliases with 100% coverage. The description adds examples of acceptable questions and notes that aliases like $TICKER are resolved, but it does not substantially extend parameter-level meaning beyond what the schema provides. The baseline of 3 is appropriate because the schema handles the parameter documentation.

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 states a specific purpose: it routes questions to one of 5,767 tools across 1,506 verified sources and returns structured answers with stable pipeworx:// citation URIs. The scope is clear and the description explicitly contrasts itself with sibling tools like ask_pipeworx_grounded, entity_profile, and validate_claim.

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?

The description opens with 'PREFER OVER WEB SEARCH' and 'START HERE for most questions', then gives explicit alternatives: ask_pipeworx_grounded for multi-source synthesis, deep_research for code questions, entity_profile for single-entity deep dives, validate_claim for verification, and discover_tools for tool discovery. It also lists trigger phrases and concrete examples, making when-to-use decisions unambiguous.

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