Excluir Perfil Compartilhado

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

The description adds behavioral details beyond the destructiveHint annotation by specifying that it requires confirm: true and is a 'operação de escrita destrutiva' (destructive write operation), which complements the annotation.

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 extremely concise: two sentences that state purpose, destructiveness, and the confirm requirement. No wasted 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 simple operation and presence of output schema, the description covers key behavioral aspects. However, it does not differentiate from sibling leave_profile, which could cause confusion.

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 50% schema description coverage, the description adds meaning for the confirm parameter by stating it must be true, but adds little for id beyond what the schema already provides. This compensates partially but not fully.

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 'Exclui um perfil compartilhado de sua propriedade' (Deletes a shared profile from your ownership), using a specific verb and resource. It distinguishes from sibling tools like create, list, leave, and update profiles.

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 mentions 'Exige confirm: true' indicating a requirement for use, but does not provide explicit when-to-use or when-not-to-use guidance versus alternatives like despezzas_leave_profile.

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