diff_node_amendments

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

No annotations are provided, so the description carries full burden. It mentions '2 RPC reads,' indicating the tool performs two network calls and is likely read-only. It also notes that amendments are compared 'by name where known,' acknowledging potential gaps. No contradictions.

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 concise with three sentences: purpose, use case, and efficiency. No unnecessary words or redundancy. Every sentence adds 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?

Given the presence of an output schema (not shown but indicated), the description need not detail return values. It covers purpose, use case, and number of RPC calls. Missing details like output format or edge cases are minor gaps.

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 0%, and the description does not elaborate on the parameters beyond the example 'mainnet vs testnet.' It does not explain the default values or behavior when both networks are the same. The schema's enum values provide the main meanings, but the description adds little.

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 it diffs enabled-amendment sets between two networks, listing what is enabled on one but not the other. It references specific networks (mainnet vs testnet) and explains why a transaction or Hook feature works on one network but not the other, distinguishing it from siblings like get_amendment_status.

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 gives a use case (explaining why a transaction/Hook feature works on one network but not the other), but does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it. The usage context is implied but not fully articulated.

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