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

With no annotations, the description carries the full burden for behavioral disclosure. It implies a read-only operation via 'List', but does not mention pagination, default limits, filtering behavior, data freshness, or potential errors. The presence of a 'limit' parameter further suggests that 'all' in the description is not literal, but this discrepancy is not addressed.

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?

A single, well-structured sentence with no redundant words. It front-loads the core action and immediately lists the key output fields. Every word contributes value.

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 simple list tool with two parameters and no output schema, the description gives the essential content (trust scores, grades, activity) but lacks important context like pagination behavior and the distinction between 'all' and the default limit. Given the simplicity, it is minimally adequate but leaves room for clarification.

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 description coverage is 100% for both parameters (limit, status), so the description does not need to explain them. The description adds no additional semantic meaning beyond the schema, matching the baseline expectation of 3 when the schema handles parameter details.

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 a specific action ('List all registered OracleNet nodes') and specifies the data returned (trust scores, grades, activity). The verb 'List' and resource 'OracleNet nodes' make the purpose unambiguous and distinguish it from sibling tools that focus on status, reputation, or trust passports.

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 provides no guidance on when to use this tool versus alternatives like quantum_reputation, quantum_trust_passport, or quantum_status. It does not state scenarios, prerequisites, or exclusions, leaving the agent to infer usage from the purpose alone.

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