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

Since no annotations exist, the description carries the full burden of transparency. It provides highly valuable business context, such as the conditional job closure logic (based on checklists), the specific status text 'Paid outside Doing Work,' and business rules like the lack of fee or limit.

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 comprehensive and long, but it is logically structured, front-loading the core function and then systematically detailing operational rules. Every sentence provides necessary business context for a complex financial tool.

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 that there is no output schema and no annotations to aid understanding, the description is remarkably complete. It covers workflow consequences, status reporting, and agent-level limitations, ensuring an agent has all necessary context to use it safely and correctly.

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 strong semantic context for the `method` parameter by detailing all allowed categories (check, cash, etc.). While the schema defines the parameters, the description explains the business relevance and scope of the tool's usage, making it highly effective despite the 50% 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?

The description immediately defines the specific purpose: recording payments received outside standard payment channels (check, cash, financing, etc.). It clearly distinguishes this tool's function by detailing its effect on job/invoice status, which differentiates it from standard payment tools.

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?

It provides explicit usage criteria by listing the allowed payment methods. Crucially, it provides critical 'when-not' or behavioral guidance by stating that this recording status means the job is 'never marked paid or verified' in the standard sense, offering precise operational constraints.

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