conversations_set_topic

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. However, it simply states the action without revealing any side effects, authentication requirements, idempotency, or error conditions. This is critically insufficient for a mutation tool.

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 extremely concise at six words, but this brevity sacrifices necessary detail. While it is front-loaded, it does not earn its place as it essentially restates the tool's name. A moderate score reflects the trade-off between conciseness and informativeness.

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 simplicity (two required parameters, no nested objects, and an output schema), the description is still incomplete. It omits crucial context such as success/failure behavior, rate limits, or required permissions. The presence of an output schema does not absolve the need for basic contextual 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?

The input schema already documents both parameters (channel and topic) with clear descriptions. The description adds no additional meaning beyond what the schema provides, which is acceptable given the 100% schema coverage. Baseline score of 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 action ('Set') and the resource ('topic for a conversation'), making the tool's purpose unambiguous. However, it does not differentiate from a sibling tool 'conversations_set_purpose', which could cause confusion without additional context.

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?

No usage guidance is provided. The description does not specify when to use this tool over alternatives, nor does it mention any prerequisites or limitations. The agent is left to infer usage from the tool name alone.

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