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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so safety is covered. The description adds genuine value by specifying the payload's content (formulas, sources, simplifications, limitations), telling the agent what it actually gets back rather than just that the call is safe.

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?

One sentence after the colon, front-loaded with the verb and resource, then the content list. No preamble and nothing redundant.

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 single-parameter read tool with rich annotations and a fully documented schema, the definition is nearly sufficient — the content enumeration removes ambiguity about return values even without an output schema. A brief pointer to list_methodology would close the last gap.

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?

There is a single parameter with 100% schema description coverage and a concrete example ('regra-de-taylor'), so the schema already carries the semantics. The description adds nothing about how slugs are formed or what happens with an unknown slug — 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 ('Devolve') and resource ('texto completo de um artigo de metodologia') and enumerates what the article contains (fórmulas, fontes, simplificações, limitações). It does not distinguish itself from its obvious sibling list_methodology, which is the only gap.

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 'texto completo' implies this is the detail-fetch counterpart to a listing tool, but that is left to inference — neither list_methodology nor any other sibling is named, and there is no explicit 'use this when' clause.

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