freee_create_deal

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Create a new deal' without mentioning any side effects, authentication requirements, rate limits, or idempotency. The agent cannot assess risks or constraints from this description alone.

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 sentence, which is concise but overly brief. While it front-loads the purpose, it leaves no room for additional useful context. Every sentence should earn its place, and here the one sentence is adequate but could be expanded with minimal added length.

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 7 parameters (3 required) and no output schema, the description should provide context about the result of creating a deal (e.g., returns an ID) or error conditions. It does not. The schema covers parameter details, but the description lacks completeness about the tool's behavior and output.

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 100%, meaning each parameter already has a meaningful description in the schema. The tool description adds no additional explanation about parameters, so it meets the baseline expectation. It does not improve understanding beyond what the schema provides.

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 'Create a new deal (transaction)' clearly states the verb 'create' and the resource 'deal', and includes a parenthetical to clarify it's a transaction. This distinguishes it from sibling tools like freee_update_deal and freee_get_deal. However, it lacks additional context about what constitutes a 'deal' in this domain, which could be clearer.

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 freee_create_deal_payment or freee_create_invoice. It neither mentions prerequisites nor when not to use it, leaving the agent to rely solely on the tool name and schema.

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