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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by disclosing the response is static markdown (confirming no dynamic computation or side effects) and includes an as_of date, which signals the content may be time-stamped and potentially dated. This goes beyond the structured 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 a single, compact sentence that packs the tool's content scope and output format without redundancy. Every clause earns its place, and the most identifying information (what it is, what it returns) is front-loaded.

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 parameterless, read-only tool with no output schema, the description fully specifies what the agent will receive (static markdown with an as_of date) and what the content covers. There is nothing an agent needs to know to invoke this correctly that is missing.

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 tool has zero parameters, so the schema imposes no burden. The description appropriately focuses on output instead of parameters. The baseline of 4 applies because there are no parameter semantics to clarify.

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 identifies the tool's resource (TradeBasis overview) and the content it provides: what TradeBasis is, the problem it solves, differentiators, and target audience. It also states the return format (static markdown with an as_of date), making the tool's purpose unmistakable and distinct from siblings focused on pricing, research, and VIN decoding.

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 when to use the tool (when an agent needs a general introduction to TradeBasis), but it does not explicitly state alternatives or exclusions. There is no mention of 'use tradebasis_pricing_and_tiers for pricing details' or similar routing, so the guidance relies on inference rather than explicit direction.

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