list_payments_applied

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

No annotations, so description must disclose behavior. Only states 'list' and filter hint; omits pagination (top/skip), sorting, field selection, and any side effects. Reads as read-only but not explicit.

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?

Extremely concise at two sentences, no redundancy. First sentence states purpose, second gives usage hint. However, conciseness sacrifices completeness.

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?

Despite having an output schema, description fails to cover pagination, sorting, and sibling differentiation. With 5 optional parameters and many siblings, more context is needed for correct invocation.

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 description should explain parameters. Only filter_expr is mentioned. Common parameters top, skip, select, orderby are not described, leaving agents to infer behavior.

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 'List payments-applied records' with a clear verb and resource. OData filtering mention adds specificity, but doesn't differentiate from siblings like list_payments_applied_for_date_range, which is a missed opportunity.

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?

Says 'Use filter_expr for OData filtering', which hints at parameter usage but gives no guidance on when to choose this tool over siblings (e.g., for general listing vs. pre-filtered lists) or when not to use it.

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