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

Description adds behavioral context beyond annotations: it returns example questions with tool+argument shapes, explains response structure, and mentions the live catalog. Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false; description is consistent and enriches understanding.

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?

Description is slightly lengthy but front-loaded with key purpose and user-targeted phrasing. Structured into variations of user questions, then explanation of returns and usage. Efficient but could be trimmed slightly.

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?

Complete for a simple tool with one optional parameter and no output schema. Covers what it does, when to use, how to invoke, and what kind of response to expect. No missing information.

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?

Input schema has 100% coverage with a clear description of the topic parameter and its possible values. Description adds usage context (e.g., 'Omit for a cross-category spread') that enhances but does not significantly surpass schema information.

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?

Description clearly states it is an onboarding entry point that suggests example questions, returning category-bucketed examples with tool and argument shapes. It distinguishes from siblings by advising to use this FIRST when unaware of Pipeworx's capabilities.

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?

Explicitly states when to use (when you don't know what Pipeworx can do, or to learn meta-tools) and how to call: with no arguments for full spread or with a topic to focus. Provides clear alternative context.

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