List Payee Bank Details

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

While the annotations indicate non-read-only (readOnlyHint: false), the description claims a creation behavior. However, the description is internally inconsistent (return vs create), and there is no mention of side effects (e.g., what gets created, if any existing data is modified). The tool name further confuses the intended 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 not concise due to contradictory statements (return vs create) and includes extraneous technical details (e.g., Procore API path). The confusion undermines the structure; a clear, single purpose is missing.

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?

The tool has no output schema, so the description should explain what is returned. It states 'returns the created object on success' but does not describe the object structure or fields. Given the creation nature, it omits important context about what is being created and the consequences.

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 100% with descriptions for both parameters. The description reiterates the required parameters but adds no additional meaning beyond the schema (e.g., data types, constraints, or relationships). For high coverage, a baseline of 3 is appropriate.

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 is contradictory: it says 'Return payee bank details' (a read action) but then immediately states 'Creates a new Payments' (a write action), with HTTP 201 on success. The tool name 'list_payee_bank_details' implies a listing operation, but the description indicates creation. This is severely misleading.

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 lists required parameters but provides no guidance on when to use this tool versus alternatives. It does not state the context or prerequisites for calling the tool, nor does it mention 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.