search_payments

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It adds useful context via the '[tier: readonly-owner]' tag, indicating a safe, read-only operation, and specifies that the tool returns IDs. This goes beyond a simple statement of purpose and aids the agent in understanding side effects.

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 two sentences plus a tag, delivering essential information (purpose, return type, endpoint, and safety tier) with no wasted words. It is well-structured 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 the tool has 7 optional parameters, no output schema, and no annotations, the description is incomplete. It explains what the tool does and returns IDs, but does not cover parameter semantics, pagination, or any filtering behavior, making it insufficient for confident 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?

The description provides no information about the 7 input parameters, which have 0% schema description coverage. It only says 'search for payments' without hinting at available filters like date range, office IDs, or payment IDs. This leaves the agent with no guidance on how to construct valid queries beyond the raw schema.

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 the tool searches for payments and returns matching IDs, with a clear verb and resource. This distinguishes it from get_payments, which presumably retrieves specific payments, and other search_* tools by specifying the resource and return type.

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 implies when to use the tool ('search for payments') but does not explicitly mention alternatives or when not to use it. While the verb 'search' suggests filtering use cases, there is no explicit comparison to sibling tools like get_payments for retrieving known IDs.

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