event_summary

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

Discloses that the algorithm is 'greedy two-pointer' to minimize transactions. Although no annotations exist, this addition provides useful behavioral context beyond a generic summary.

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?

Efficient bulleted list plus a brief algorithm note. Every sentence adds value with no redundancy.

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 presence of an output schema, the description adequately covers the tool's output components (expenses, balances, settlements) and algorithmic detail, making it complete for its purpose.

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 has one parameter (event_id) with 0% description coverage. The description does not explicitly describe event_id, but its purpose is inferable from context. Baseline for low coverage is 3, as description adds limited meaning.

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?

Clearly states it provides a complete event summary including expenses, net balances, and settlement transactions. Distinct from sibling summary tools by specifying comprehensive components.

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?

Implied usage as the go-to for overall event financial summary, but no explicit guidance on when to use alternative tools like expense_summary or settle.

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