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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the core safety profile is covered. The description adds a meaningful trait beyond that: the word 'owned' indicates the tool only retrieves brands the caller owns, which is a scoping constraint not present in annotations. This extra context justifies a score above baseline.

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 sentence, ten words, with the verb front-loaded. There is no filler or redundancy, and it directly conveys the core function and output contents. It is as concise as possible while being informative.

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 get-tool with one parameter and no output schema, the description adequately tells an agent what to expect: a brand identity with voice, value proposition, and guidelines. The 'owned' qualifier sets expectations about access. It does not cover error behavior or authorization requirements, but those are not critical for a read-only, idempotent operation.

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 input schema provides full description coverage for brand_id ('Full UUID from the matching list tool'), so the schema carries the semantic load. The description itself adds no additional meaning about the parameter, just the generic 'one' which is redundant. Thus a baseline score of 3 is appropriate.

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 clearly states the action ('Get') and the resource ('one owned brand identity'), and specifies what the result includes (voice, value proposition, guidelines). It distinguishes from list_marketing_brands by saying 'one', and from other get_* tools by naming brand-specific content. However, it does not explicitly name any sibling, so it falls short of a 5.

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. It does not mention that list_marketing_brands should be used to enumerate brands, nor any conditions that would select this tool over create/update or other get tools. The only related clue ('Full UUID from the matching list tool') lives in the input schema, not in the description.

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