expensify_list_expenses

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

No annotations are provided, so the description carries full responsibility. It mentions routing under JWT, tenant, and company scope, adding some security context, but fails to disclose behavioral traits like pagination, error handling, data freshness, or whether the tool makes external API calls.

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 brief but includes verbose routing details that could be omitted. The core purpose is buried. It is reasonably concise but not optimally structured for quick comprehension.

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?

While an output schema exists, the description lacks completeness by not clarifying the behavior or expected format of the arguments parameter. Given the low schema coverage, the description should compensate but does not.

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?

The single parameter 'arguments' is a JSON string with 0% schema coverage, and the description does not explain its purpose, expected format, or required keys. The agent gains no insight beyond the schema itself.

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 identifies this as a platform tool for listing expenses from Expensify via a connector operation, which distinguishes it from list_policies and list_reports. However, it does not explicitly state the output (list of expenses) and focuses on routing details, making the purpose only moderately clear.

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?

No guidance is provided on when to use this tool versus other expense-related tools or alternatives. The description lacks context about prerequisites, filtering, or typical use cases.

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