aruba_get_invoice_timeline

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

The description adds no behavioral information beyond what annotations already declare (readOnlyHint, destructiveHint, idempotentHint, openWorldHint). It doesn't mention side effects, required permissions, or output characteristics. The description carries a low burden due to rich annotations but fails to add any context.

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 a single sentence, which is concise and front-loaded. However, it is too terse to be informative; it sacrifices necessary detail for brevity. It earns a middle score because it is not verbose but is under-specified.

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 3 parameters with no schema descriptions, no explanation of the output timeline, and a rich set of sibling tools, the description is severely incomplete. It does not tell the agent what the timeline contains, how parameters affect it, or how it compares to other invoice tools. The presence of an output schema is noted, but without any context, the agent cannot use the tool effectively.

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 description coverage is 0%, and the description does not explain any of the three parameters (direction, filename, confirm_read). No semantic meaning is added beyond the parameter names themselves, which are ambiguous (e.g., direction could mean 'ascending/descending' or 'sent/received'). The description fails to compensate for the missing schema descriptions.

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 clearly states the tool builds a timeline from invoice metadata and SDI notifications, which is a specific verb and resource. It distinguishes from siblings as no other sibling mentions 'timeline'. However, it doesn't explain what the timeline represents or its format, so clarity is slightly reduced.

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 alternatives. The description lacks any context about typical use cases, prerequisites, or scenarios where this tool is preferable to others. This forces the agent to infer usage from the tool name alone.

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