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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the concrete API mapping (GET /v1/produtos/{codigo}), which confirms it is a plain read, but says nothing about what 'full data' includes, whether related entities are embedded, or how a missing code is handled.

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 compact sentences, with the operation and scope front-loaded and the endpoint mapping as supporting detail. No filler or redundancy.

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 single-parameter read-only getter this is close to sufficient, and annotations carry the safety profile. But 'full data' is undefined and there is no output schema to compensate, so an agent cannot anticipate the response shape or whether nested product data is included.

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 100% and the single parameter already documents itself as 'The record code (from the matching list tool).' The description's 'by code' restates the schema without adding format, range, or lookup-source detail, 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 and resource ('Get full data of one product by code'), which is enough to tell it apart from egestor_list_products and egestor_list_services, which return collections rather than a single record. It never names a sibling explicitly, so differentiation is implied 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?

'Get full data of one product by code' implies the usage pattern (fetch a single record's details, presumably after finding the code in a list), and the schema note 'from the matching list tool' reinforces that. However, there is no explicit when-to-use/when-not guidance and no mention of error behavior for an unknown code.

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