Criar Perfil Compartilhado

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

Annotations already include destructiveHint: true, and the description adds the specific requirement of confirm: true, which is a behavioral constraint. It also clarifies the operation is a 'write' and specifies the three profile types, providing context beyond 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?

The description is a single sentence plus a brief requirement note. It is front-loaded with 'Operação de escrita' and contains no redundant 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?

The description covers the core action and critical parameter (confirm), but omits details about invites (max 5 items), name length constraints, and potential errors like duplicates. The output schema exists but is not referenced.

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 description adds meaning by linking the type parameter to the three profile types and emphasizing the confirm parameter requirement. However, it does not explain the name constraints or the invites parameter structure, leaving some gaps despite 50% schema coverage.

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 it is a write operation that creates one of three specific extra profiles (PJ, family, investments). It distinguishes from siblings like delete_profile and switch_profile by explicitly naming the types and using 'cria' (creates).

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 advises that confirm must be true, which is a critical prerequisite. However, it does not explicitly state when to use this tool over alternatives like despezzas_update_profile_access or despezzas_switch_profile, though the sibling list implies distinct purposes.

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