process_mail_account

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

With no annotations provided, the description carries the full behavioral burden. It does disclose a key side effect: processing 'can consume matching mails according to enabled Paperless mail rules', which warns that mail may be removed/changed. However, it omits permissions required, idempotency, whether the run is synchronous, and failure behavior.

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?

Two compact sentences with the action front-loaded and the side-effect caveat second. No filler, though the second sentence is somewhat hedged ('can consume').

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 trigger/mutation tool with no annotations and no output schema, the description covers the core action and the consuming side effect but leaves meaningful gaps: prerequisites, whether the account must be enabled, sync/async behavior, and result reporting. Adequate but not complete.

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% for the single 'id' parameter, so the description must compensate. Saying 'for one account' hints that id is a mail account identifier, but it adds no format, valid-range, or sourcing detail beyond what the bare integer schema implies.

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?

States a specific verb and resource: 'manually run Paperless mail processing for one account'. This clearly distinguishes it from read-oriented siblings like get_mail_account and list_mail_accounts. It is not fully differentiated from other triggering actions, but the action is unambiguous.

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 word 'Manually' implies this is an on-demand trigger rather than a scheduled process, which is useful context, but the description never states when to use this versus letting rules run automatically, nor any prerequisites (e.g., account must be configured/enabled). Usage is only implied.

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