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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuine data-scoping disclosure ("returns only data visible to the linked Market Brew account"), which is beyond the annotations, but says nothing about behavior when the asset is missing or inaccessible.

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 with no filler, and the trigger is front-loaded. Nothing is padded, though the brevity reflects under-specification rather than tight writing.

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 one-parameter tool with no output schema and 0% schema description coverage, the description should clarify what an asset is and what is returned. It leaves the return shape and parameter semantics entirely unexplained, relying only on annotations for the safety profile.

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 assetId parameter, and the description provides no meaning, format, or sourcing guidance for it. The name is self-suggestive, but the description does nothing to compensate for the undocumented parameter.

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 essentially restates the tool title ("get a Content Booster asset") without adding a distinguishing verb scope or resource detail. It does not differentiate from close siblings such as get_content_booster or list_content_booster_assets, so an agent cannot tell which to pick from the description alone.

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?

"Use this when the user asks to get a Content Booster asset" is a circular trigger condition that gives no real when-to-use context. No alternatives are named (get_content_booster, list_content_booster_assets) and no prerequisites or exclusions are stated.

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