sei_renunciar_credenciamento

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description explains that the user loses access and provides error recovery advice ('Se falhar com erro inesperado, use sei_versao para verificar a versão instalada'). 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?

Three concise, front-loaded sentences: purpose, effect, and error recovery hint. No fluff, every sentence adds value.

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 description covers purpose, effect, and error handling but omits parameter details and return value (output schema exists but is not described). Adequate for a simple tool but not comprehensive.

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% and the description does not elaborate on the 'processo' parameter (e.g., format or identifier type). The parameter name is self-explanatory given context, but the lack of explicit semantics for an AI agent is a gap.

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 'renunciar' (renounce) and resource 'credenciamento de acesso a um processo sigiloso'. It distinguishes from siblings like sei_conceder_credenciamento and sei_cassar_credenciamento by specifying self-renunciation.

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 implies usage for voluntary self-renunciation ('O próprio usuário perde o acesso'), but does not explicitly state when not to use or mention alternatives. Sibling tools provide context, but explicit guidance is missing.

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