Excluir Perfil Compartilhado

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

Description adds the confirm requirement beyond annotations. Annotations already indicate destructiveHint=true and idempotentHint=true, which are consistent. No additional behavioral details like error cases or irreversible effects.

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 short, front-loaded sentences with no redundant information. Every word is essential for the purpose and requirement.

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 annotations provide destructive/idempotent hints, the description is passable but minimal. It lacks information about prerequisites (e.g., ownership is implied but not explicit in text) and potential side effects on associated data.

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 coverage is 0%, so description should compensate. It explains the confirm parameter (must be true), adding value beyond the default=false in schema. However, the required 'id' parameter is not described at all.

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?

Clearly states the action (Exclui = delete) and resource (perfil compartilhado próprio = own shared profile). Differentiates from siblings like despezzas_leave_profile (leave vs delete) and despezzas_create_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?

Mentions the requirement confirm=true, but provides no guidance on when to use this tool versus alternatives (e.g., despezzas_leave_profile for shared profiles not owned). No 'when not to use' or context for decision-making.

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