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

Goes well beyond the readOnly/idempotent annotations: it discloses billing behavior (1 credit, not charged on miss), data provenance (legislatie.just.ro, Ministry of Justice), and a substantive authenticity caveat that consolidated forms are unofficial and only Monitorul Oficial text is authoritative. These are exactly the operational and trust facts an agent can't infer from structured fields.

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?

A single dense but well-ordered block: what you get first, then format edge cases, then cost and provenance. Every clause carries information, though the run-on pricing/source sentence could be split for scannability.

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?

With no output schema, the description does the work of explaining return content (paragraph/letter structure, dated amendment notes), which is the key missing piece. It leaves the miss case underspecified — 'not billed if not found' implies an empty/error result but doesn't say what is actually returned.

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%, so both parameters are already documented with the same examples ('171282', '293^1'). The description restates the article-number format edge case and adds a semantic hint (VAT rates for art. 291) but contributes no new syntax or constraints, so 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?

States a specific resource at a precise granularity ('one article in its current consolidated form') with a concrete worked example (Codul fiscal 171282 art. 291) and the shape of the payload. It implicitly contrasts with get_legal_act and search_legislation by emphasizing a single article, but never names those siblings, so the differentiation is inferential rather than explicit.

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 through the example and the 'costs 1 credit' note; there is no statement of when to prefer this over get_legal_act (full act) or search_legislation (find the right id/article). An agent must guess its own routing rather than being told.

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