ramp_list_receipts

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

With no annotations, the description carries full burden. It mentions routing via JWT and scope but does not disclose behavioral traits such as read-only nature, side effects, auth prerequisites, error behavior, or rate limits. For a list tool, it fails to state it is a safe read operation.

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 and front-loaded, but it lacks substance. While it contains no wasted words, it is overly minimal and does not provide enough information to be useful.

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's simplicity but missing annotations, the description is incomplete. It does not explain the purpose of the 'arguments' parameter, expected format, or any prerequisites. The existence of an output schema does not compensate for the lack of behavioral context.

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 0%, so description must compensate. The only parameter is 'arguments' described as 'JSON string of arguments for the connector operation'. This adds minimal meaning; no structure, examples, or allowed keys are provided.

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 'Ramp connector operation list_receipts', clearly indicating the verb (list) and resource (receipts). The purpose is discernible, though no further context about what receipts are in Ramp is provided. It distinguishes from sibling tools like ramp_list_reimbursements and ramp_list_transactions by name alone.

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 usage guidelines are given. The description does not specify when to use this tool versus its siblings (ramp_list_reimbursements, ramp_list_transactions), nor does it provide any context on appropriate scenarios or alternatives.

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