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

No annotations are provided, so the description carries the full behavioral burden. Implicit read-only semantics come from 'Read', but nothing is said about which credential (agent_key vs api_key) is required, whether results are paginated, scoped by time, or what happens if the caller is not a funder. This is a significant gap for a tool with zero annotation coverage.

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 front-loaded sentence with no filler; the resource and scope are stated immediately. It is appropriately sized, though the brevity comes at the cost of missing details rather than being efficiently complete.

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?

For a two-parameter read tool with no output schema and no annotations, the description leaves key call-time questions unanswered: which credential form is expected, whether the identity must be a registered funder, and what the accrual results represent. The identity scoping note is useful but insufficient on its own.

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 neither 'agent_key' nor 'api_key' is referenced in the description. The only hint is 'the calling funder identity', which weakly implies the credential determines the funder scope, but it does not explain the oneOf requirement or which key applies in which situation.

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 states a clear verb ('Read') and a specific resource ('royalty recovery and credit accruals') scoped to 'the calling funder identity'. An agent can tell this apart from generic read tools like balance_get or agent_earnings_get. However, it does not explicitly name a sibling or contrast the royalty domain with those adjacent money-related readers.

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 mention of alternatives such as agent_earnings_get or balance_get. The phrase 'for the calling funder identity' implies the caller must be a funder, but this constraint is not framed as a usage condition or exclusion.

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