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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds a distinct behavioral requirement: 'REQUIRED: Disclose as Sponsored Brand Content.' This goes beyond the annotations and provides actionable context about how the output must be handled. It does not contradict the annotations.

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 extremely concise, with two sentences: the purpose and a critical requirement. The purpose is front-loaded, and there is no extraneous detail. Every word earns its place, making it highly efficient and easy to parse.

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?

Despite having an output schema and high schema coverage, the description lacks contextual grounding. It does not explain when to use this tool versus sponsored_search, nor does it clarify what constitutes 'storytelling' or how the tool integrates into the broader shopping context. The required disclosure is useful, but the description is too sparse to fully equip an agent for correct invocation in diverse scenarios.

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 baseline is 3. The description does not add any additional meaning to the parameters — it does not explain brand_query, tenant_id, or context beyond what the schema already describes. It neither compensates nor detracts from the schema, so the baseline 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 states a clear verb and resource: 'Get sponsored brand content and storytelling.' This is a specific action and is not a tautology. However, it does not explicitly differentiate itself from the sibling tool 'sponsored_search', which likely serves a similar purpose. A bit of differentiation would elevate it to 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?

There is no guidance on when to use this tool versus alternatives like sponsored_search. The only usage note is 'REQUIRED: Disclose as Sponsored Brand Content,' which is a compliance instruction rather than a selection criterion. No exclusions or alternative conditions are provided, so an agent gets no help in choosing this tool over its siblings.

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