Conduit

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

Annotations provide significant behavioral hints: readOnlyHint=false (implies mutation), idempotentHint=true (safe to retry), destructiveHint=false (non-destructive). The description adds context by specifying that it's for communication with Figma and describes the return format, which is useful beyond annotations. However, it doesn't cover aspects like rate limits, authentication needs, or error conditions.

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 front-loaded, with the main purpose stated first and return details following. It uses two sentences efficiently, though the return format explanation could be slightly more streamlined (e.g., by omitting redundant 'type: text' detail if not critical).

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 has 1 parameter with full schema coverage, annotations covering key behavioral traits, and no output schema, the description is moderately complete. It explains the purpose and return format but lacks details on error handling, side effects, or when to use alternatives, leaving some gaps for a mutation tool.

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%, with the parameter 'channel' clearly documented in the schema as 'The name of the channel to join. Must be a non-empty string.' The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 where 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 action ('Join a specific channel') and the purpose ('to communicate with Figma'), which is a specific verb+resource combination. However, it doesn't distinguish this tool from its many siblings (like 'subscribe_event' or other communication-related tools), as the sibling list doesn't show obvious alternatives for joining channels.

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 (e.g., whether the channel must exist or if authentication is needed), nor does it reference any sibling tools for comparison, despite the long list of siblings that might include related functionality.

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