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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds the content domain (what rules exist) but says nothing about the form of the answer — whether it returns a single text block, per-topic sections, or how the trade-in ('Troca Certa') rules are structured. Useful but not rich.

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 front-loaded sentence with a colon introducing the topic list; the domain ('marketplace iHelpU') comes first and every clause carries content an agent can match a user question against. No filler.

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 zero-parameter, no-output-schema informational tool, the description sufficiently covers what subject matter is available. The only gap is that it does not indicate how the content is returned or whether it is exhaustive across those topics.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the tool is a no-argument, topic-scoped lookup.

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 the resource precisely: purchase rules for the iHelpU marketplace, enumerating the covered topics (pickup in stores, deadlines, warranty, payment, trade-in, service area). It is not a verb-driven action but the informational scope is unambiguous. Sibling tools (buscar_iphones, detalhes_aparelho, lojas_ihelpu, preco_iphone_usado) are about concrete objects/prices, so the topical separation is largely implicit rather than stated.

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: an agent can infer this is the tool for process/policy questions and not for phone listings or prices. There is no explicit 'use this when...' clause and no routing away from lojas_ihelpu, which also covers store-related information and is the most likely confusion point.

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