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

With no annotations, the description carries the disclosure burden. It warns 'PAID (x402)' upfront and details return content, which is valuable. However, it does not mention other behavioral traits such as rate limits, authentication needs, error handling, or whether it's read-only.

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 highly concise: two short sentences with the cost warning front-loaded. Every clause adds value, efficiently conveying both the paid nature and the scope of the returned data.

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?

Given the simple structure (one parameter, no output schema, no annotations), the description adequately covers return content and the cost caveat. It lacks details on vendor identifier format or error scenarios, but for a straightforward retrieval tool, it is sufficiently complete.

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 only defines a 'vendor' string with no description, and the description adds minimal semantic value by saying 'for one vendor.' This clarifies the parameter's role but provides no format, example, or allowed values, leaving the agent to infer what string to use.

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 tool returns a 'full source-cited data-trust record for one vendor' and enumerates the content (every field, quote, source URL, confidence, date). This specific scope distinguishes it from sibling tools like get_ai_vendor_trust_headline (likely a summary) and get_ai_vendor_trust_compare (likely multiple vendors).

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 this tool by emphasizing 'full' and 'for one vendor,' which signals it is for complete single-vendor lookups rather than headline or comparison variants. It does not explicitly name alternatives or exclusions, but the context is clear enough.

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