Listar Perfis do Despezzas

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

With no annotations, the description carries the full burden. It discloses that the tool lists 'owner and member' profiles, which is helpful. However, it does not mention any potential constraints (e.g., workspaces, pagination) or the fact that it is safe (non-destructive). The description is adequate but not rich in behavioral detail.

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 extremely concise with two short sentences. Every word serves a purpose: the first sentence states the action, the second gives usage guidance. No filler or redundancy.

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 has no parameters and an output schema (not shown), the description covers what the tool does and when to use it. It could mention the output structure briefly, but it is likely provided by the schema. The description is complete for its simplicity.

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 tool has no parameters (schema coverage 100%), so the description does not need to add parameter details. The baseline score for 0 parameters is 4, and the description meets this without unnecessary information.

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 'Lista perfis Despezzas de proprietário e membro' indicating it lists profiles, distinguishing it from other list tools like list_accounts. However, it does not explicitly contrast with the sibling tool 'despezzas_profile', which might retrieve a single profile.

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 explicitly advises to use this tool before switching profile context or managing shared profiles, providing clear context for when to invoke it. It does not mention when not to use it or alternative tools, but the guidance is sufficient for a simple listing tool.

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