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

The annotations already declare readOnlyHint=true and destructiveHint=false, so no safety caveat needs to be repeated. However, the description adds no behavior context beyond a one-line summary; it does not disclose the return format, potential failures, or any special runtime behavior. For an operation that may return image data or a URL, this is a meaningful gap.

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 a single concise sentence with no fluff. 'Gets the company logo from BRC' is front-loaded and communicates the entire purpose without unnecessary wording.

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?

The tool is simple, has only one required parameter, and is read-only, so the description is minimally viable. However, there is no output schema, and the description would be stronger if it clarified how the logo is returned (e.g., as a URL, base64, or binary data).

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 input schema already documents both parameters clearly, including the important connectionRef semantics. The description itself adds no parameter details, but per the baseline for high schema coverage, this is acceptable even if not additive.

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 a specific verb ('Gets') and a specific resource ('company logo'), making the tool's purpose clear. It is naturally distinct from the many brc_get_* siblings due to the unique 'company logo' resource, though it does not explicitly call out any sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives, and no exclusions or alternative names are mentioned. The detailed connectionRef parameter guidance is helpful for session handling, but it does not explain usage context for the loo-fetching operation itself.

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