search_ksef_invoices

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'query' implying read-only, but does not disclose any behavioral traits like pagination, rate limits, or whether it modifies data. Insufficient for safe usage.

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 a single sentence of 8 words, which is concise but under-specified for the tool's complexity. It is front-loaded but sacrifices necessary detail, making it barely adequate.

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 3 parameters (one with default), no annotations, and the need for usage guidance, this description is incomplete. It lacks parameter details, behavioral traits, and usage context. An agent would struggle to use it 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?

Schema description coverage is 0% and the description adds virtually no parameter meaning beyond 'date range'. It does not explain the subject_type parameter or its default value. For a tool with 3 parameters, the description fails to compensate for empty schema descriptions.

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 'Query invoices stored in KSeF for a date range' uses a specific verb (Query) and resource (invoices in KSeF) with clear scope (date range). It distinguishes from sibling tools (generate, submit, validate) by focusing on searching/querying existing invoices.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it, prerequisites, or any conditions. Siblings suggest it's for retrieval, but explicit guidance is missing.

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