Criar Perfil Compartilhado

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

Annotations already indicate the tool is not read-only (readOnlyHint=false) and not idempotent. The description adds the requirement for 'confirm=true', which is useful but does not disclose other behaviors like error handling or side effects beyond creation.

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 concise sentence that conveys the core purpose and a key requirement. It is front-loaded but could include more context without becoming verbose.

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 tool's complexity (4 parameters, including optional nested invites) and the existence of an output schema, the description covers only the bare minimum. It lacks explanation of the return value, the invites parameter, and the effect of 'confirm'. The description is incomplete for a create operation.

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 parameter description coverage is 0%, so the description must add meaning. It mentions the 'type' enum values (PJ, família, investimentos) and the 'confirm' requirement, but does not explain 'name', 'invites', or the meaning of 'confirm' itself. This is insufficient for a 4-parameter tool.

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 tool creates an extra profile (PJ, family, investments). It distinguishes from sibling tools like 'despezzas_list_profiles' and 'despezzas_create_account' by specifying the resource (profile) and subtypes.

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 notes that 'confirm=true' is required, giving a usage constraint. However, it does not provide guidance on when to use this tool versus alternatives (e.g., 'despezzas_create_account'), nor does it mention prerequisites 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.