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

readOnlyHint=true already covers the safety profile, so the bar is lower; the description still adds value by disclosing the returned object's shape (type, name, start, next number, default) and the underlying endpoint. It does not mention pagination, auth requirements, or rate limits, keeping it short of a 5.

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?

Very compact: the resource and its fields are front-loaded, followed by a terse usage tip and the GET path. No filler, though the parenthetical field list is dense and 'Use the name as series_name' is slightly cryptic out of context.

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 single-parameter, read-only lookup with annotations covering safety and no output schema, the description compensates by listing the returned fields. Missing only minor details such as what 'default' and 'next number' signify or whether the result is paginated.

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 100% and the single cif parameter is already explained (format plus example RO37311090 and its source from oblio_list_companies). The description adds nothing about the parameter, so the baseline 3 applies.

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 names a specific resource ('Document series of a company') and enumerates the fields it carries (type Factura/Proforma/Aviz, name, start, next number, default), so an agent knows exactly what it retrieves. No sibling lists series, so there is no real ambiguity, though the description doesn't explicitly differentiate itself from siblings.

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?

Usage is only implied: you call it to inspect a company's series definition. It gives one actionable workflow hint ('Use the name as series_name'), but no explicit when-to-use, prerequisites, or alternatives for other lookups.

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