Add an expense to XMemo

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

Annotations are minimal (readOnlyHint false, destructiveHint false) and the description adds little beyond stating it records an expense. No mention of auth requirements, rate limits, or side effects. With annotations present, the description should add context but fails to do so.

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?

Two sentences clearly stating purpose and usage. Very concise and front-loaded with the core action. No wasted words, though the second sentence is slightly long but still efficient.

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?

With 16 parameters and an output schema, the description covers the core recording action sufficiently. It does not explain relationships to sibling tools or error handling, but the output schema exists and the usage guidelines are adequate.

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 coverage is 100%, so baseline is 3. The description mentions capturing date, amount, etc., which maps to parameters, but adds no extra meaning beyond the schema descriptions. It does not clarify parameter interactions 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 starts with a specific verb 'Record' and resource 'one expense in the XMemo Ledger'. It clearly differentiates from sibling tools like list_ledger_transactions by focusing on recording, not querying. The examples clarify the scope.

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?

Provides clear guidance: 'Call this whenever the user states a concrete expense... not only on an explicit record this.' It gives concrete examples, though it does not explicitly state when not to use or list alternatives, which would elevate the score.

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