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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the description is not required to restate those. It adds useful behavioral context: the analysis is specific to wire and international bills, returns estimated savings, and requires prior connection. No contradictions with annotations.

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 three sentences, front-loaded with purpose, followed by return values and a requirement. Every sentence adds value with no redundancy or filler. Perfectly concise and well-structured.

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 that an output schema exists (documented elsewhere), the description sufficiently covers what the tool does and returns. It mentions the key return items (cross-border totals, top vendors, savings) and the prerequisite. No critical gaps for an analysis tool with robust annotations and schema.

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?

Both parameters (tenant_id, page_size) have descriptions in the input schema (100% coverage). The description only adds that a connected account is needed, which is already implied by tenant_id. It does not add meaningful detail beyond what the schema provides, earning a baseline score of 3.

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 explicitly states the verb 'Analyse' and identifies the specific resource: 'a connected Ramp account's wire and international bill volume' with a clear objective 'to surface DPX settlement opportunity.' It lists the returns (cross-border totals, top vendors, estimated savings), making it distinct from sibling tools like ramp.connect or ramp.settle.

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 includes a prerequisite ('Requires Ramp account connected via ramp.connect') and implies usage for assessing DPX settlement opportunity. However, it does not explicitly state when not to use it or compare it to other analytical siblings (e.g., compute.cost), leaving some ambiguity for alternative selection.

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