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

Annotations already establish read-only, open-world, idempotent, non-destructive behavior. The description adds valuable behavioral detail: it is the default entry point, works on every tier, makes one fast call, routes across 5,724 tools, and returns stable pipeworx:// citation URIs. It could mention failure or limitation behavior, but the annotations carry the safety profile, so this is strong.

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 densely information-rich, with the most important directive front-loaded ("PREFER OVER WEB SEARCH"), followed by domains, examples, and explicit escalation paths. No sentence is wasted; each earns its place by telling the agent when and how to use the tool.

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?

For a broad, default-entry factual lookup tool with no output schema, the description is complete enough: it defines coverage, explains what the response will contain (structured answer with citation URIs), gives examples, and clarifies relationship to siblings. An agent can confidently decide to invoke this tool across a wide range of queries.

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%, so the schema fully documents the single required question parameter and its aliases. The description contributes example queries and confirms natural-language input but does not add substantial semantics beyond what the schema already provides. Baseline 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 verb and resource: ask a factual question, route it across thousands of verified sources, and return a structured answer with citation URIs. It explicitly differentiates itself from siblings by naming ask_pipeworx_grounded and deep_research and by positioning itself as the default entry point.

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 triggers ("what is", "look up", "find", "get the latest", etc.), domain categories, and concrete examples. It also prescribes when to step up to alternatives: hallucination-resistant answers use ask_pipeworx_grounded, broad/multi-part questions use deep_research. This is unusually actionable routing guidance.

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