Assistant Manage Tool

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

Beyond the destructiveHint annotation, the description details authorization levels per action, notes that send_message triggers a synchronous tool-loop LLM call consuming team credits, and explains that conversation_clear erases all messages. This adds valuable behavioral context not captured in 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 with bullet points for each action. It front-loads the purpose and efficiently covers authorization, parameters, and side effects without unnecessary verbosity.

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 description is thorough for a tool with multiple actions, covering purpose, authorization, parameter behaviors, and destructive effects. However, it lacks details on return values for actions like list/get, which would improve completeness for an agent.

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?

Input schema has 100% description coverage, but the description adds usage context (e.g., omit conversation_id to start new, optional limit and context_type filter for conversation_list). This provides meaningful guidance beyond the schema itself.

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 that the tool manages FleetQ AI assistant conversations, listing specific actions (conversation_list, conversation_get, send_message, conversation_clear). It distinguishes itself from sibling tools by focusing on the in-app chat panel that can call MCP tools, making its purpose unambiguous.

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 clear context for when to use each action based on authorization roles (read for all, write for Member+, destructive for Admin/Owner). However, it does not explicitly exclude alternatives among sibling tools or specify when not to use this tool, missing a small opportunity for clearer guidance.

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