get_ap_payment_status

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

The only behavioral disclosure is 'Fails loudly', which indicates error behavior but lacks details like read-only intent, authorization requirements, or what happens on missing data. With no annotations, the agent is left to infer most behavioral traits.

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 extremely brief but at the cost of missing essential information. It includes an arguably irrelevant version note and a behavioral hint, but fails to explain the parameter or usage. It is under-specified rather than efficiently 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?

Given the tool has a single parameter with no schema documentation and no annotations, the description should provide more context. It lacks details on how to invoke the tool, what context is needed, and how it differs from sibling tools. The presence of an output schema does not compensate for missing input semantics.

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 description coverage is 0%, yet the description provides no explanation for the sole parameter 'fields_json'. Its purpose (whether to specify the payment ID or select fields) is entirely unclear, forcing the agent to guess. This is a critical gap.

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 states 'AP payment status', clearly indicating the tool retrieves the status of an accounts payable payment. The name itself is descriptive, and it is distinguishable from siblings like get_ap_bill and get_ap_vendor. However, it lacks detail on how the tool identifies which payment, relying on the vague 'fields_json' parameter.

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?

No guidance is provided on when to use this tool versus alternatives. The note '[Not in LCS /v1]' hints at scalability or deprecation but does not offer explicit usage context or prerequisites. The agent receives no help in deciding if this tool is appropriate.

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