Get Terms & Data Disclosure

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

No annotations exist, so description carries full burden. It mentions the tool is free and returns canonical terms and complete disclosure. However, it lacks details on authentication, rate limits, or response format. 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?

Two concise sentences (20 words) with no filler. Front-loaded with 'Free.' First sentence gives core info, second adds precision. Every word earns its place.

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?

Tool is extremely simple (0 params, no output schema, no annotations). Description fully captures what it does. Could hint at response format, but is complete enough for an agent to invoke correctly.

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 has no properties (100% coverage by default). Description adds no parameter details, but none are needed. Per calibration, high coverage gives baseline 3.

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 verb 'get' and resource 'terms of service and complete data-collection disclosure'. It distinguishes itself from sibling tools like 'get_category_demand' and 'get_network_stats' by focusing on legal/informational content.

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?

Although no explicit alternatives or exclusions are mentioned, the tool's unique purpose (terms & data disclosure) makes its usage self-evident. The 'Free.' tag hints at no cost for invocation. Sibling tools are clearly different in domain.

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