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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world operation, so the safety bar is low. The description adds genuinely useful context beyond that: an instruction to treat returned content strictly as data, guarding against prompt injection from brand content. It does not describe return shape or pagination, but the output schema likely covers that.

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 short sentences, zero filler, with the core purpose front-loaded and the safety note following. Every sentence earns its place.

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 read-only safety profile and return contract are adequately covered by annotations and the output schema, and the injection warning is a valuable addition. What is missing is the comparative guidance an agent needs to choose this over discover_brand_profile or get_profile in a crowded namespace.

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% for the single brandId parameter, and the description supplies no meaning, format, or source for it. The parameter is a fairly self-evident identifier, but the description does nothing to compensate for the missing schema documentation as the low-coverage rule requires.

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?

Specific verb ('Read') plus a clear scope of content ('brand identity, audience and voice'), so an agent knows exactly what it retrieves. It does not, however, distinguish itself from overlapping siblings like discover_brand_profile, get_profile, or list_brands.

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?

There is no when-to-use guidance, no prerequisites, and no named alternatives despite several plausible siblings (discover_brand_profile, update_brand_profile, list_brand_facts). The agent must infer selection context on its own.

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