Editar Perfil Compartilhado

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

Annotations indicate destructive and idempotent. The description adds that invites replace the current list and requires confirm=true. This goes beyond annotations but does not cover all behavioral traits (e.g., confirmation effect, side effects on other fields).

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 sentences, no fluff, key points about behavior and requirement. However, could be more concise if additional details were added without bloating.

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 5 parameters with no schema descriptions, the description is insufficient. It omits explanations for id, name, type, and does not mention output or conditions. Required confirm=true is stated but not elaborated. Agent would need to infer or rely on other sources.

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 explain parameters. It explains 'invites' (replaces list) and 'confirm' (must be true), but leaves id, name, and type unexplained. Only two of five parameters are addressed.

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 edits a shared profile (verb+resource). It distinguishes from sibling update tools by specifying 'perfil compartilhado' and mentions that invites replace the current list. However, it could be more explicit about the access aspect.

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 explicit guidance on when to use versus alternatives. The only usage direction is 'Exige confirm=true', which is a requirement, but no context about prerequisites or exclusions.

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