aruba_get_sent_notifications_by_invoice_id

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds little beyond mentioning 'Sensitive' and 'Base64', which might be inferred from the output schema. No contradiction, but minimal added value.

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 extremely short but lacks substance. Conciseness should not sacrifice clarity; here it is under-specified, failing to convey key information.

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 low schema coverage and existence of an output schema, the description should clarify what 'sent notifications' are, what 'Base64 read' means, and how 'confirm_read' affects behavior. It does none of these, leaving major gaps.

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%, so the description must compensate. However, it does not explain the 'invoiceId' path parameter or the 'confirm_read' boolean. The agent receives no help on parameter meaning or usage.

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 'GET /services/notification/out/{invoiceId}. Sensitive notification Base64 read' is vague about what exactly the tool returns (the notification? Its Base64-encoded content?). It does not distinguish it from siblings like aruba_get_sent_notifications_by_invoice_filename or aruba_get_received_notifications_by_invoice_id.

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 (e.g., by invoice ID vs filename, sent vs received). The description does not specify context or exclusions.

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