Conduit

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the return format but doesn't cover critical aspects like whether this is a read-only operation, error handling, rate limits, or authentication needs. For a tool that queries data, this lack of behavioral context is a significant gap.

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 in two sentences: one stating the purpose and another detailing the return format. It avoids redundancy and is front-loaded with the core functionality. A slight improvement could be adding usage context, but it's efficient as is.

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 moderate complexity (querying variants/properties), lack of annotations, and no output schema, the description is partially complete. It covers the purpose and return format but misses behavioral traits and usage guidelines. For a read operation, this is adequate but leaves gaps that could hinder effective tool use.

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 input schema already documents both parameters ('componentSetId' and 'componentSetIds') with clear descriptions. The description adds value by explaining the return format differences for single vs. batch queries, which helps interpret the parameters' effects. However, it doesn't provide additional semantic details beyond what the schema offers.

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 info about variants/properties for one or more component sets.' It specifies the verb ('Get info') and resource ('variants/properties for component sets'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'get_components' or 'get_node_info', which might also retrieve component-related data.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as whether component sets must exist, or compare it to sibling tools like 'get_components' or 'set_variant'. The agent must infer usage from the purpose alone, which is insufficient for optimal tool selection.

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