set_evolution_settings

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

With no annotations provided, the description must fully disclose behavioral traits. It only says 'update,' implying mutation, but does not mention side effects, required permissions, or what happens to existing settings. The description adds minimal transparency beyond the tool name.

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 a single short sentence, which is concise but does not add substantial value. It is not overly verbose, but it could be more structured to include key details without being longer.

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 tool has eight parameters and no output schema, yet the description provides almost no context about what settings are affected or how they change behavior. The description is insufficient for an agent to understand the full scope of the tool's functionality.

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 only 25% (two out of eight parameters have descriptions), and the tool description provides no additional meaning for any parameter. It fails to compensate for the low coverage, leaving seven parameters undocumented in both schema and description.

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 states the tool updates 'behaviour settings of an instance,' but it lacks specificity about what kind of instance (Evolution API) and does not distinguish it from similar sibling tools like 'set_evolution_presence' or 'set_evolution_webhook'. The verb is clear, but the resource is vague.

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 guidance is provided on when to use this tool versus alternatives. For example, it does not mention that 'get_evolution_settings' should be used for reading or that an instance must exist first. The agent is left without context for proper usage.

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