anaf_tokens

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond annotations by explaining what each token represents and what fields are returned (token ID, CIF, expiry, validity status); it does not contradict the annotations.

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 three sentences with no wasted language. It front-loads the primary purpose, then explains token meaning, then documents return fields in a natural order.

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 simple zero-parameter list tool with rich safety annotations and no output schema, the description is complete. It says what is listed, the scope, what a token represents, and which fields are returned, leaving no significant ambiguity for an agent.

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 and the schema is empty, so the baseline is 4. The description does not need to compensate for parameter documentation and appropriately focuses on the resource and return fields instead.

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 ('List') and resource ('ANAF OAuth tokens') along with scope ('authenticated user') and business meaning ('enables e-Factura synchronization for a specific company CIF'). It does not explicitly name or differentiate itself from sibling tools such as anaf_status or anaf_create_token_link, which keeps it just below the top score.

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 usage by explaining that tokens enable e-Factura sync, so an agent can infer this is the tool to inspect existing tokens. However, it gives no explicit when-to-use guidance, no exclusions, and no mention of alternatives like anaf_create_token_link or anaf_delete_token.

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