Criar Transação

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

Annotations are all false (no readOnly, no idempotent, etc.), so the description carries full burden. It adds behavioral context by noting the confirm flag requirement and the prepare recommendation, but does not disclose side effects, error conditions, or return behavior.

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?

Extremely concise: two sentences with no fluff. The main action and crucial usage notes are front-loaded. Every word serves a purpose.

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?

Despite having an output schema, the description is too sparse for a 16-parameter mutation tool. It omits details on required fields (title, amount_cents, date), optional fields, and parameter interplay. The prepare-first recommendation is helpful but insufficient for confident agent invocation.

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 description coverage is 0% (no parameter descriptions in schema). The tool description does not explain any of the 16 parameters, such as title, amount_cents, kind, etc. It only mentions confirm and prepare, which are not parameter-specific explanations. Considerable gap.

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 'Cria transação' (Creates transaction), a specific verb+resource combination. The mention of required confirm and recommended prepare distinguishes it from sibling tools like update or delete transactions.

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?

Explicitly states the requirement to set confirm=true and recommends running the prepare step first (via sibling despezzas_prepare_create_transaction). Provides clear context for correct invocation, though does not explicitly list when not to use.

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