ecount_web_export_tax_invoices

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

With no annotations, the description carries full burden and does an excellent job. It discloses the OAPI limitation, web-session-based behavior, headless login via env vars, return format (columns/rows/count), failure conditions (RuntimeError on missing trusted device or 2FA), and the required first-time manual setup. This is comprehensive.

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 moderately detailed but well-structured with clear sections (main description, returns, note). Each sentence provides value, including the reference to implementation docs and the bootstrap step. Slightly verbose but appropriate for the complexity.

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?

For a no-parameter tool, the description covers the purpose, return structure, prerequisites, and failure modes. It also references additional documentation. It could be slightly more explicit about what the column/row data contains, but given an output schema exists, this is sufficient.

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 input schema has zero parameters, so the baseline is 4. The description mentions environment variables used for login, but these are not tool parameters and are contextually useful. No parameter confusion exists.

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 clearly states that it extracts a purchase electronic tax invoice list via a web session, with a specific screen (ECTAX102M). It distinguishes itself from siblings (save/call tools) by focusing on export/read, and mentions an OAPI limitation that makes this tool necessary.

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 explains when to use the tool (because OAPI does not support this feature) and provides a prerequisite (one-time manual login for trusted device registration). However, it does not explicitly name alternative tools or give exclusions, 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.