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

With no annotations, the description carries the full burden. It discloses the read-only/past nature via 'Historical' and the default page size of 30, which are useful behavioral traits. However, it omits pagination, result ordering, and any authorization/permission context for a market-maker-specific endpoint.

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?

Two short, front-loaded sentences that lead with what the tool returns and then cover the optional filter, with no wasted words. 'LQF' is unexplained jargon, a minor structure cost.

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 3-param, no-annotation, no-output-schema read tool, the description covers the core purpose and two of three params but leaves the required user_id, domain term LQF, and any pagination/ordering behavior unspecified. Adequate but with clear 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 coverage is 0%, so the description must compensate; it covers market_id as an optional filter and the default limit of 30, which adds real meaning. But the required user_id parameter is never mentioned, leaving a critical input undiscussed.

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: retrieves historical LQF stipend payouts for a market maker, which is distinct from the read concept of estimate. It implicitly contrasts with the sibling mm_stipend_estimate (estimate vs. actual past payouts), but never names it, so the differentiation is left to inference.

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 explicit when-to-use guidance and no alternatives named. An agent can infer 'read past payouts' from 'Historical', but there is no condition telling it when this tool is preferred over mm_stipend_estimate or fee_ledger_read.

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