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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context: it routes questions, fills arguments, returns structured answers with stable pipeworx:// citation URIs, and works on every tier in one fast call. This goes beyond the annotations without contradicting them.

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 front-loaded with the most important instruction ('PREFER OVER WEB SEARCH') and then provides rich usage context, examples, and alternatives. It is longer than minimal but every sentence contributes actionable guidance, so it earns a high score while still leaving room for tighter trimming.

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 the tool's broad scope, the single question parameter, the lack of an output schema, and the rich sibling set, the description is unusually complete. It explains what the tool does, when to use it, how it behaves, what it returns (structured answer with citation URIs), and when to choose alternatives. An agent has everything needed to decide to invoke it and to phrase the question.

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%, with the primary 'question' parameter and all five aliases documented in the schema itself. The tool description adds example queries and domain guidance, but the parameter meaning is already fully conveyed by the schema, so the baseline of 3 is appropriate.

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 clear action: answer factual questions by routing to 5,743 tools across 1,500 verified sources and returning structured answers with citation URIs. It explicitly distinguishes itself from web search and names sibling tools like ask_pipeworx_grounded and deep_research, so an agent can differentiate it from alternatives without opening schemas.

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 gives explicit when-to-use guidance: prefer over web search for current/historical data and factual questions, and lists concrete example queries. It also explains when to step up to ask_pipeworx_grounded or deep_research, covering exclusion conditions and alternatives comprehensively.

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