getCreditCard

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The phrase 'Detalhar cartão de crédito' only implies a read operation but does not disclose return behavior, error handling, or permissions. It offers no more information than the tool name itself, failing to add behavioral context.

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 very brief ('Detalhar cartão de crédito') and could be considered concise, but it is under-specified. It is not a complete sentence and lacks detail, making it more of a label than a useful description. It does not fully convey the tool's function in a structured way.

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 simplicity of the tool (1 parameter, no annotations, but an output schema exists), the description is still inadequate. It does not state what the tool returns or the context in which it should be used. The phrase 'Detalhar cartão de crédito' is too vague to provide complete context, even for a simple get-by-ID 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?

The schema has one parameter 'id' with no description (0% coverage), and the description does not mention this parameter at all. It fails to compensate for the schema's lack of detail. While the parameter name 'id' is somewhat self-explanatory, the description adds no meaningful explanation about its role or constraints.

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 'Detalhar cartão de crédito' translates to 'Detail credit card', which provides a verb and resource but is vague. It does not explicitly state that this tool retrieves a single credit card by ID, nor does it distinguish from the sibling tool getCreditCards (plural). The purpose is somewhat clear but lacks specificity.

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 provides no guidance on when to use this tool versus alternatives such as getCreditCards or updateCreditCard. There is no mention of context, prerequisites, or exclusions, leaving the agent without direction for tool selection.

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