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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' is redundant. However, the description adds rich behavioral context beyond annotations: ranked candidates by evidence, what is missing, warnings, and a start date adjusted for what an earlier connector already booked. That is meaningful disclosure of semantics and state the agent would otherwise not know.

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?

It is appropriately front-loaded (subject and scope stated first), but it is one enormous run-on sentence with many comma-linked clauses that makes the inventory of returned data hard to parse. Every clause carries content, so the problem is structure rather than padding.

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 and only one parameter, the description carries the return-value burden and does so thoroughly, enumerating the 90-day metrics, balance, per-choice candidates, missing items, warnings, and suggested start date. It is complete enough to call correctly, though usage context versus siblings is the remaining gap.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already fully explains 'company'. The description adds nothing about the parameter, which is acceptable at this coverage level but earns no bonus.

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 is highly specific about the resource and payload: the connected Stripe account's last 90 days, balance, and per-setup-choice candidate mappings with missing items, warnings, and a suggested start date. An agent can tell this is the read/prefill view of payout configuration. It stops short of naming get_payout_status or save_payout_setup as the sibling it is not, so it does not fully differentiate.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives. The 'Read-only' tag implies it precedes save_payout_setup, but that is left entirely to inference, and nothing distinguishes it from get_payout_status.

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