Get distribution payment list

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true. The description adds two genuinely useful traits beyond that: results are written to a JSON file and only returned inline when small, and the payload contains investor personal data, which flags sensitivity. It does not say how large 'small' is or how to retrieve the file when it is not inlined, so the delivery mechanism stays partly opaque.

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?

A single dense sentence covering payload contents plus two short clauses on delivery and data sensitivity. Front-loaded with what the tool returns and zero filler.

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?

With no output schema, the description does the work of listing the returned columns, which is what an agent needs to decide relevance. The gap is the file-vs-inline handoff: it never explains how the agent gets the JSON file when the response is too large to return inline.

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 100% and both parameters are documented with their source tools (list_issuers, list_distributions). The description adds nothing about the parameters themselves - the listed fields are return values, not inputs - so baseline 3 applies.

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?

States a specific verb-resource pair ('per-holder payments for a distribution') and enumerates the payload contents (components, tax, DRP, net amount, payment method). It is clearly distinguishable from report-building siblings, though it does not explicitly name an alternative.

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 when-to-use guidance, no prerequisites, and no exclusions. The agent must infer from the required distributionId and the sibling list_list_distributions that this is a per-distribution drill-down rather than a report generator; nothing in the text says so.

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