Sair de Perfil Compartilhado

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

The description adds the confirm requirement beyond annotations (destructiveHint=true, idempotentHint=true). However, it does not disclose side effects like irreversibility, impact on other members, or required permissions, which would be valuable for a destructive tool.

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 concise sentences, front-loaded with purpose and followed by a crucial requirement. No superfluous information.

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?

Despite an output schema being present, the description lacks detail on return values, prerequisites, or side effects for a destructive tool. The minimal information may confuse the agent about when and how to safely invoke it.

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 must compensate. It clarifies that confirm must be true for the action to proceed, but provides no semantics for profile_id (only that it is required). This partially compensates.

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 'leave' and resource 'profile', indicating it removes the account from a shared profile. It distinguishes from siblings like delete_profile (which deletes the profile) and switch_profile (which changes active profile), but does not explicitly differentiate.

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?

No guidance on when to use this tool vs alternatives. The description only states the action and requirement for confirm=true, leaving the agent to infer usage context from the name and siblings.

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