anaf_sync_log

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

With no annotations provided, the description carries the full behavioral disclosure burden. It clearly states the tool is read-only (retrieval of a log) and specifies the fixed window (last 50 invoices). However, it doesn't disclose the return format/structure, whether results are paginated, or any ordering guarantees beyond 'recent'.

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, tight sentence in active voice that efficiently communicates the purpose, scope, and content of the returned data. Every clause earns its place — no filler, no redundancy.

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?

This is a simple, parameterless read tool with no output schema required. The description fully explains what the user gets (log entries with 4 fields each) and the fixed limit (50). There is no complexity that demands additional disclosure, and with no parameters and no annotations needed, the description is complete for its simplicity.

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 tool has zero parameters, so there is no parameter schema for the description to add meaning to. The baseline for 0 parameters is 4, and the description appropriately covers what data the log contains without needing parameter documentation. It correctly describes the fixed nature (always last 50, no filtering options).

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 states a specific verb+resource ('Retrieve the recent e-Factura sync activity log') with clear scope ('last 50 synced invoices') and details the content of each entry (invoice ID, company CIF, sync timestamp, status). This clearly distinguishes it from siblings like anaf_sync_trigger and anaf_sync_status, which deal with triggering and status checking rather than log retrieval.

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 implies this is for viewing historical sync activity, which is a clear enough context. However, it doesn't explicitly state when to use this vs anaf_sync_status (which likely shows current sync state) or anaf_sync_trigger (which initiates a sync). The distinction is implied by the 'log' framing but not explicitly stated.

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