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

With no annotations, the description carries the full behavioral burden. It implies a read-only, auth-scoped operation ('current builder') and hints at two fee categories, but says nothing about pagination behavior (despite a cursor param), result shape, retention windows, or rate limits.

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 the resource named first and the returned content types appended. Nothing is wasted; it is only slightly terse given the query parameters it must support.

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 time-ranged, cursor-paginated read with zero annotation coverage, no output schema, and 0% parameter documentation, the one-line description is not sufficient. It should at minimum describe the time-range and pagination semantics.

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% for three parameters, and the description adds no parameter meaning beyond the names. It never explains that from_ms/to_ms are epoch-millisecond bounds or how cursor is used for paging, so an agent gets no semantic help at all.

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 (Read) and resource (fee_ledger entries), scoped to 'the current builder', and even enumerates the content types returned (4-way split shares + additive builder fees). It is clearly distinguishable from siblings like fee_estimate or mm_stipend_history, though it never names an alternative explicitly.

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 mention of prerequisites, and no routing to alternatives such as fee_estimate (projection) vs this ledger (actuals). The scoping phrase 'attributed to the current builder' is the only hint, leaving invocation context largely to inference.

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