Tuanjie Dialog Manager

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

Annotations already indicate destructiveHint=true and non-idempotent behavior, so the safety profile is covered. The description adds that parameters are passed through unchanged and that the context is a modal editor dialog, but it does not explain what the click actually applies to or what side effects may occur.

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 short and front-loaded with the core action. Both sentences earn their place, though 'Supported actions: click' is mostly redundant with the verb 'clicks'.

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?

This is a destructive tool with no output schema and no parameter-level documentation. The description omits how the target dialog or button is identified, what the accepted pass-through parameters are, and what consequences the click may have, leaving an agent with insufficient detail to invoke it reliably.

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 0% and the description only restates the 'click' enum value without adding meaning. The claim that additional action-specific parameters are passed through unchanged is useful, but no names, types, or purposes are provided, so the description does not compensate for the schema's total lack of parameter documentation.

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 action and resource: it clicks a button in a modal editor dialog. This distinguishes it from the sibling tools by focusing on dialog interactions, though it doesn't explicitly contrast itself with any sibling.

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 implies when to use the tool: whenever a click action in a modal editor dialog is needed. However, it provides no explicit when-not-to-use guidance or alternatives, leaving the selection logic largely inferred.

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