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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description aligns by saying 'Leitura de ofertas'. It adds useful behavioral context beyond annotations: the concept of an offer as a price unit and order-bump target, plus bulk execution support.

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?

The description is well organized: a one-line purpose, a brief domain concept explanation, and bulleted actions. It is not overly verbose, and every part adds context, though the list-action section is somewhat redundant given the flattened-get framing and sibling list tool.

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 read tool with 10 optional-looking schema parameters and no output schema, the description covers the main use cases and bulk behavior. It leaves gaps: the relationship between get/list is muddled, the account parameter is undocumented, and the response shape is not described.

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 0%, so the description must carry parameter meaning. It maps most parameters to their roles: product, status, type, search, ordering, limit, and page for filtering; offer_id for single detail; offer_ids for bulk. It omits the 'account' parameter and doesn't explain enum values, but it compensates reasonably for the schema's lack of descriptions.

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 states the tool reads Cakto offers and clearly identifies the get action as retrieving details of ONE offer requiring offer_id, with bulk support via offer_ids. It distinguishes single-offer retrieval from listing, though it also documents the list action and there is a sibling cakto_offers_list, which introduces some ambiguity.

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 description implies the get path should be used when offer_id is available and says offer_ids are accepted for batch execution, giving some contextual guidance. However, it never explicitly says 'use cakto_offers_list for listing/searching' and actually lists list-related filters even though the tool is flattened to the get action.

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