listar_artigos

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

No annotations are provided, so the description carries the full burden. It only states 'List all available articles' without disclosing whether it is read-only, what 'all' means (e.g., pagination, limits), or any potential side effects. Minimal behavioral context.

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?

Two sentences efficiently convey purpose and parameter details. No fluff, but could be slightly improved with a note on return format or placement in a broader workflow.

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?

Given the low complexity (1 optional parameter) and presence of an output schema, the description is minimally adequate. It states the action but does not explain what fields the list contains or how results are structured, relying on the output schema.

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 parameter 'lang' is described with explicit allowed values ('pt', 'en', 'es') and a default ('pt'), adding meaning beyond the schema's type and default. However, no details on case sensitivity or format validation.

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 'List all available articles' uses a specific verb and resource, clearly indicating what the tool does. It distinguishes itself from sibling tools like 'get_artigo' (single article) and 'search_artigos' (search with filters).

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'get_artigo' for a specific article or 'search_artigos' for filtered queries). There is no mention of limitations or use cases.

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