Listar Perfis do Despezzas

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating safe, repeatable reading. The description adds context by specifying it 'informa o perfil ativo' (reports the active profile), which goes beyond the annotations and improves understanding of the output.

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, clear sentence that conveys all necessary information without any redundant or unnecessary words. Every phrase earns its place.

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, an output schema exists to document return values, and annotations fully cover safety behavior, the description is complete enough. It informs the agent of the exact purpose (list profiles with active info) and no further context is required.

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?

There are no parameters, so schema coverage is 100% by default. The description adds no parameter-specific information, which is acceptable since none exist. Baseline score of 4 is appropriate for a parameterless 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 lists profiles (owner and member) and identifies the active profile. It uses a specific verb ('Lista') and resource ('perfis'), and the mention of 'informa o perfil ativo' adds distinct value. Among siblings, this tool is distinct as a list operation versus singular retrieval (despezzas_profile) or mutations (create/delete/switch).

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 this tool versus alternatives. However, its purpose is straightforward (listing profiles) and sibling names like 'despezzas_profile' (singular) and 'despezzas_switch_profile' imply different use cases. The description does not provide explicit exclusions or scenarios.

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