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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context by explaining the return format (category-bucketed example questions with tool + argument shape), that it draws from a live catalog, and that calling with no arguments gives the full spread. 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 a single paragraph that front-loads the tool's intent with trigger phrases, then explains the return type, the topic parameter, and the recommended usage. While somewhat dense, every sentence adds meaningful information and there is no filler. The length is justified given the need to convey the tool's value and usage in an onboarding context.

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?

The tool is simple (one optional parameter) but lacks an output schema, so the description carries the burden of explaining what the tool returns. It does this thoroughly: the return is category-bucketed example questions with exact tool + argument shapes, drawn from the live catalog. It also explains the no-argument vs. topic behavior and when to use the tool. The description is fully complete for this tool's complexity.

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 provides 100% coverage with a detailed description for the optional `topic` parameter, listing valid focus areas and indicating to omit for a general spread. The description adds examples like 'finance', 'pharma', 'betting' and explains that passing topic focuses the response, but this largely reflects the schema's existing information. The baseline of 3 is appropriate since the schema does the heavy lifting.

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 the tool's purpose as 'the onboarding entry point for an agent that just connected and wants to know what is worth asking.' It specifies the resource (Pipeworx) and the action (suggest questions), and distinguishes it from siblings by noting it returns tool + argument shapes for example questions. This is a specific verb+resource description.

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 explicitly says 'Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools.' This provides clear when-to-use guidance and points to related meta-tools, but it does not explicitly state when not to use it or name alternative tools. It effectively conveys the intended context without exclusions.

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