etsy_payment_ledger_entries_list

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

The description repeats the read-only hint already provided by annotations but adds no extra behavioral context. It does not mention pagination (limit/offset), filtering (min_created/max_created), or any side effects, leaving the agent uninformed about the tool's operational behavior.

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, concise sentence, efficiently communicating the main purpose. However, it lacks structure and additional details that could aid understanding, such as parameter usage or filtering options, making it slightly too terse.

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?

Given the tool's complexity (5 parameters, no output schema), the description is incomplete. It omits pagination, filtering, required parameter details, and relationship to sibling tools, leaving significant gaps for an agent to interpret.

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?

With only 40% schema description coverage, the description fails to add meaning for three out of five parameters (shop_id, limit, offset) which lack schema descriptions. It does not compensate by explaining the role of these parameters, forcing the agent to rely on external knowledge.

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 action (list) and resource (financial ledger entries) for a shop, providing a basic understanding. However, it does not distinguish from the sibling tool 'etsy_ledger_entries_list', which likely lists general ledger entries, missing an opportunity to clarify the 'payment' specificity.

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 offers no guidance on when to use this tool versus alternatives like 'etsy_ledger_entries_list' or 'etsy_payment_ledger_entry_get'. There is no mention of prerequisites, such as the required shop_id, or typical use cases.

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