excluir_perfil_usuario

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

No annotations are provided, so the description carries full burden. It discloses that this is a soft delete and warns about potential failures or consequences if the profile is linked to users. It does not detail success responses or authentication needs, but the key behavioral trait is clear.

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 well-structured: purpose, historical context, prerequisites, and caution. It is front-loaded with the main action. The historical note about the test script is slightly extraneous but does not significantly detract from clarity.

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 delete tool with one parameter and no output schema, the description covers the action, effect, input source, and risks. It provides sufficient context for an AI agent to use the tool appropriately.

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?

The input schema has no description for the single 'id' parameter (0% coverage). The description compensates by explaining that the ID should be obtained via 'buscar_perfis_usuario', giving semantic meaning to the parameter.

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 the verb 'Excluir' (delete) and resource 'perfil de usuário (nível de acesso)' from Ploomes CRM, specifying it is a soft delete. This distinguishes it from other sibling delete tools like 'excluir_cliente' or 'excluir_produto'.

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 provides a clear prerequisite: use 'buscar_perfis_usuario' to obtain the profile ID. It also includes a caution about deleting profiles linked to users. However, it lacks explicit guidance on when to use this tool versus alternatives or when not to use it.

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