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

No annotations are provided, so the description carries the full behavioral disclosure burden. It reveals the output fields, ordering (newest first), and limit semantics. It does not mention error handling, authentication, or rate limits, but for a simple read-only history tool, this level of disclosure is reasonable.

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 description is a single, information-dense sentence plus a limit note. Every word earns its place: it states the resource, ordering, and exact return fields. There is no fluff or repetition, making it exceptionally concise.

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, the description appropriately lists all returned fields, which is crucial for the agent to understand the response. It lacks details on status values or pagination behavior beyond the limit, but for a 2-parameter list tool, it is sufficiently complete.

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 descriptions cover 100% of parameters (limit, agent_id), and the description essentially restates the limit range/default already present in the schema. It adds no new semantic meaning beyond the schema, so it meets the baseline of 3 for high schema coverage.

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 clearly states the tool returns 'your past withdrawals' and lists the returned fields, which distinguishes it from related tools like get_balance or get_my_history. It lacks an explicit verb, but the tool name 'get' makes the action clear.

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?

The description implies the tool is for viewing withdrawal history, mentioning order and limit, but does not explicitly state when to use it over alternatives (e.g., get_my_history or check_payout) or provide exclusion criteria. No alternatives are named.

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