evolution_instance_set_presence

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

Description indicates a mutation ('Set') but lacks details about side effects, authorization requirements, or impact on instance connections. No annotations provided to compensate.

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?

Single sentence with no fluff, front-loaded with verb and resource. Every word is informative, and the parentheses efficiently communicate options.

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?

For a simple two-param tool with no output schema, the description covers core purpose adequately. Missing some usage context but complete enough for basic usage.

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?

With 100% schema coverage, the description adds value by summarizing the effect on presence state and noting optional instance parameter. The enum values are restated, providing clarity.

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?

Description clearly states the action 'Set' and the resource 'global presence of an instance' with possible values in parentheses. It distinguishes from sibling tools like evolution_chat_send_presence by targeting instance-level presence.

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?

Description implies when to use (for instance presence) but does not explicitly exclude alternatives or provide context like when to use chat-level presence instead. No 'when-not' guidance.

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