get_terms

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

With no annotations provided, the description carries full burden and adds valuable behavioral context: it discloses cost ('FREE to call'), authentication requirements ('no API key required'), and output format ('Returns full legal JSON'). It doesn't mention rate limits or error behavior, but covers key operational aspects.

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?

Three tightly packed sentences with zero waste: first states purpose, second provides usage rules and cost, third describes output. Every sentence earns its place by adding distinct, essential information.

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 0-parameter tool with no annotations or output schema, the description provides complete context: purpose, usage rules, cost, authentication, output format, and content details. It compensates for missing structured fields with clear natural language explanation.

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 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, maintaining focus on tool purpose and usage.

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 specific action ('Retrieve'), resource ('machine-readable Terms of Service for the HederaIntel MCP Platform'), and scope ('full legal JSON'). It distinguishes from siblings by focusing on terms retrieval rather than account, contract, or token operations.

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?

Explicitly states when to use ('All agents MUST call this tool... before using any paid tool'), when not to use (implied: not for operational tasks), and names the alternative/next step ('call confirm_terms'). Provides clear prerequisites and sequencing guidance.

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