Get Tool Cluster

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral context by explaining that the tool returns a complete set of tools including primary and dependencies, and provides a sample output structure. No contradictions with annotations.

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 concise and well-structured: a one-sentence title, a brief explanation of how it works, then clearly labelled Args and Returns sections. Every sentence adds value with no redundancy.

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 has three parameters with full schema coverage, and the description provides a detailed output example including fields like primary, dependencies, context, and stats. Although no output schema exists, the example sufficiently describes the return value for an agent to use the tool correctly.

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 coverage is 100%, and the description repeats parameter definitions with slight elaboration (e.g., 'Natural language task description' for query). Since schema already provides descriptions, the description adds marginal value. 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 clearly states the tool's purpose: 'Get a complete tool cluster for a task query.' It explains it combines vector search and graph expansion to return primary tools, dependencies, and context. This distinguishes it from siblings like toolhub_search (likely semantic matches only) and toolhub_expand (graph expansion on a single tool).

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 tool for complete task setup - returns everything needed to start working.' This gives clear guidance on when to use it, but does not explicitly mention when not to use it or compare with alternatives beyond the description of what it returns.

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