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

No annotations provided, so description carries full burden. It discloses the type of information returned (purchase-related) and provides contact info, but lacks details on data source, freshness, or any side effects. Adequate for a simple read-only tool.

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?

Single sentence efficiently conveys key information: purpose, minimum order, and contact. No wasted words, though could be better structured with bullet points for clarity.

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?

Covers main topics and contact info but does not specify output format (e.g., text, URL). Given no output schema and simple info retrieval, this is a minor gap. Sibling overlap with get_batch_purchase_policy is noted but not addressed.

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?

No parameters exist in the schema (100% coverage). Description adds meaning by explaining what the tool returns, compensating fully for the empty schema. Baseline for 0 params is 4.

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?

Description clearly states the tool retrieves purchase-related information including ordering guide, installation, after-sales, and bulk policy. It's specific about the resource but does not explicitly differentiate from sibling tools like get_batch_purchase_policy, which may cause overlap.

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?

Implies usage for purchase queries by listing covered topics and mentioning minimum order quantity. However, no explicit when-to-use or when-not-to-use guidance, nor comparison with siblings.

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