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

Annotations already declare readOnlyHint=true, and the description adds context about the 'public' nature and the 'concise' format. It specifies the included data types, which helps set expectations for the response, without contradicting the read-only annotation.

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 entire description is one sentence with a front-loaded action, followed by a clear list of included fields. It conveys all necessary information without unnecessary words.

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?

Given the tool's simplicity (one read-only parameter, no output schema), the description adequately covers what the brief contains including scores, strengths/weak spots, prompts, citations, related brands, and next questions. It could mention the input format, but that is a parameter semantics issue rather than contextual completeness.

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?

The single required parameter 'slug_or_id' has no description in the schema (0% coverage), and the description only indirectly mentions it by targeting 'one brand'. No format, example, or clarification is provided, leaving the parameter semantics under-specified.

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 ('Fetch') and clearly defines the resource ('concise public marketing brief') and scope ('for one brand'). It enumerates the brief's contents, which differentiates it from sibling tools like parse_get_stats and parse_get_prompt that focus on specific data slices.

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 this tool is for retrieving a holistic overview of a brand's AI visibility, but it does not explicitly state when to use it versus alternatives like parse_get_stats or parse_get_prompt. No exclusions or alternative recommendations are provided.

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