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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read-only nature is handled. The description adds value by stating the output is static markdown and that the briefs are authored by TradeBasis, giving the agent expectations about content freshness and provenance without contradicting any 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?

Two sentences cover the resource type, the call pattern, the parameter semantics, and the return format. Every clause earns its place, and the primary purpose is front-loaded. No filler or redundant restatement of the title exists.

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?

With a single optional parameter, full schema coverage, and read-only annotations, the description covers everything an agent needs: the two invocation modes, what the parameter means, and what the response looks like. There is no missing detail that would prevent a correct call.

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 schema already describes the optional topic parameter, but the description adds meaning by explicitly clarifying that the value can be a slug or title and that omitting it lists all briefs. This augments the schema rather than merely repeating it, so it earns above the baseline.

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 this tool provides static research/market-report briefs authored by TradeBasis, and it specifies the two operational modes: list all briefs with no arguments, or retrieve a single brief by topic. This gives a specific, unambiguous verb-resource pairing that distinguishes it from the sibling tools (about, pricing, vin decode).

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 explains exactly when to call with no arguments vs. when to pass a topic, which is the primary usage decision an agent faces. It doesn't explicitly name the sibling alternatives or state when not to use this tool, but the sibling names are self-explanatory and the research-brief scope is clear, so the usage context is well covered.

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