create_expense

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

With no annotations, the description must disclose behavioral traits. It only states the action and clarifies two parameters, but does not discuss side effects (e.g., whether totals are updated), authorization needs, or error states. The lack of annotation support makes this insufficient.

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 short (two sentences) but due to the tool's complexity (8 parameters), it is under-specified. Every sentence is relevant, but the brevity sacrifices completeness.

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 lack of annotations, 8 parameters, and the presence of an output schema, the description is incomplete. It does not explain all parameters, return values, or behavioral context needed for an agent to use the tool correctly.

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%, so the description must explain parameters. It only explains 'cost' (per-unit) and 'entry_date' (format), leaving 6 of 8 parameters (including required activity_name) unexplained. This adds limited value beyond the schema.

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 states 'Create an expense entry' which is a specific verb and resource. It also clarifies that cost is per-unit cost and provides date format, making it clear what the tool does. This distinguishes it from sibling create tools like create_time_entry.

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 create_time_entry or other create tools. There is no mention of prerequisites, filtering, or business logic that would help an agent decide context.

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