List Early Pay Programs

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds pagination behavior and return type (paginated JSON array with metadata). Does not disclose further behavioral aspects like authorization or rate limits, but annotations cover safety.

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?

Four sentences, each essential: purpose, usage, return description, pagination control, required parameter, and API endpoint. Efficient and front-loaded.

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 rich annotations and full schema coverage, description is complete: explains return type, pagination, required parameter. No output schema, but description covers return structure. Siblings exist but not required for completeness.

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?

Input schema has 100% coverage (4 params described). Description adds that page and per_page control pagination and response includes pagination metadata. Does not explain the sort parameter, but baseline is 3 due to 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?

Clearly states it returns all early pay programs for a company. Mentions paginated overview, finding IDs, filtering. Distinguishes from siblings like show_early_pay_program, create_early_pay_program, etc. by listing vs other operations.

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?

Explicitly says 'Use this to enumerate Payments when you need a paginated overview, to find IDs, or to filter by query parameters.' Provides clear usage context. Does not mention when not to use or alternatives like show for a single program, but the guidance is adequate.

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