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

With no annotations provided, the description itself must carry behavioral weight. 'Retrieve' reasonably signals a non-mutating read operation, which is useful. However, it does not describe edge-case behavior such as what happens when no facts exist, whether all facts are returned or only the latest, or how brand matching works. The output schema may cover some of this, but the description adds little beyond the verb.

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 one short, front-loaded sentence with no filler or redundancy. Every word contributes to the core meaning of the 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 simple one-parameter tool with a complete input schema and an output schema present, the description is largely sufficient. The only meaningful gap is the lack of explicit usage guidance relative to sibling tools, but the core call pattern is clear.

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%, so the single parameter brand_name is already well documented. The tool description adds no additional meaning about the parameter beyond what the schema states, so the baseline score 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?

The description uses a specific verb ('Retrieve') plus a clear resource ('previously stored facts about a brand'). This distinguishes it from the sibling tools: list_brands deals with brand entities, and remember implies storing new facts, whereas this tool retrieves existing fact data.

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 'previously stored' implies this tool is for recalling existing facts rather than creating or updating them, which gives some usage context. However, it never explicitly names alternatives like remember or list_brands, and it does not state when the agent should NOT use this tool.

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