Trocar Perfil Ativo

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

The description explicitly calls it a write operation and requires confirm: true, adding behavioral context beyond the destructiveHint annotation. No contradiction with 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?

Two sentences that are front-loaded with the main purpose and an important requirement. No unnecessary words.

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 output schema exists and the parameter schema explains profile_id, the description covers the main effect. Some might expect preconditions (e.g., must have profiles), but the context is sufficient.

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 50%, but the description does not add meaningful parameter details beyond what the schema already provides (e.g., profile_id description). The confirm parameter lacks explanation of its role beyond 'exige confirm: true'.

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 it switches the active Despezzas profile for future calls, using a specific verb and resource. This distinguishes it from sibling tools like despezzas_create_profile or despezzas_delete_profile.

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 indicates it requires confirm: true, providing a usage condition. However, it does not explicitly specify when not to use this tool or mention alternatives, though siblings are clear.

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