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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds the ordering guarantee (most recent first), which is genuinely behavioral information, but says nothing about pagination, truncation, or the default/maximum count 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?

A single short sentence with the resource and the scoping condition front-loaded; no redundant or filler wording.

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 two-parameter read-only listing with full schema coverage and annotations, the description covers purpose and scope sufficiently. A brief note on whether results are paginated or what an empty result looks like would make it complete, but no critical information is missing.

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 coverage is 100% and the 'limite' description already spells out range 1-30, default 10 and ordering; 'assunto' is documented as an optional subject identifier. The description reinforces the recency ordering but adds no format or syntax detail beyond the schema, 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?

States a specific verb ('Lista') and resource ('os artigos mais recentes') plus the scope ('de todos os assuntos ou de um só'), so an agent can tell this is a recency-ordered listing rather than a text search. It does not name the sibling buscar_artigos, so the distinction from search must be inferred from the wording.

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 phrase 'de todos os assuntos ou de um só' implies the optional subject filter is the only branching decision, which is useful context. However, there is no explicit guidance on when to prefer this over buscar_artigos or ler_artigo, and no note on what happens when no results exist.

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