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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful context: public data only, source reads used, no minepoa.com read, and no key handling or submission. It also discloses the return structure in detail, which compensates for the absence of an output schema.

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?

The purpose is front-loaded, and most content is relevant given the tool's rich return shape without an output schema. However, the description is a dense run-on with nested parentheticals, making it harder to scan than necessary.

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 complex diagnostic tool with no output schema, the description is complete enough: it explains when to use it, what data sources it uses, the major return sections, and the safety constraints. An agent has sufficient information to invoke it correctly.

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?

The schema fully documents the single address parameter, including its poa1 pattern and base58 format. The description adds little parameter-level meaning beyond saying it operates on one poa1 address, so the schema is doing the substantive work.

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 specific diagnostic resource: an earn check for one poa1 address, with named sections such as history, grading, and ways. It is clearly more specific than a generic lookup, but it does not explicitly differentiate itself from siblings like get_payout_outlook, get_standing, or get_onboarding_steps.

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?

It gives a clear triggering context: use when an Agent asks why it shows 0 POA or how to start earning. It also includes safety guidance about never asking for keys or submitting on the user's behalf, but it does not name alternatives or exclusions.

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