tochka_check_invoices

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

Description discloses that the tool 'automatically removes paid ones from tracking,' which is a behavioral trait beyond the 'openWorldHint' annotation. It also explains fallback matching criteria in detail, adding useful context.

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?

Description is well-structured with bullet points and front-loaded main purpose. Slightly verbose but efficient, no wasted sentences.

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's complexity (two strategies, auto-removal, fallback criteria) and the existence of an output schema for return values, the description is complete and covers all essential behavioral aspects.

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?

Only one parameter 'days' with default 30. The input schema has no description, but the description explains it as 'Statement depth in days for fallback (default 30),' which adds necessary meaning.

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?

Description clearly states the tool checks pending invoices for payment and automatically removes paid ones. It distinguishes between two strategies (with/without document_id), which differentiates it from sibling tools like 'tochka_pending_invoices' or 'tochka_track_invoice'.

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?

Provides explicit guidance on when to use each strategy (with/without document_id) and fallback criteria. However, it does not explicitly state when not to use this tool versus alternatives, but the context is clear enough.

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