approve_operator

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It warns that an approved operator can move ALL names on the contract and includes a security warning. However, it does not mention transaction costs, authority requirements (e.g., only the owner may call), or reversibility details beyond the 'approved' boolean, leaving some behavioral aspects implicit.

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 well-structured with clear sections (summary, contracts, use cases, addresses, warning) and is front-loaded with the core purpose. It is a bit long due to including contract addresses, but each section adds value and no sentence is filler.

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 absence of an output schema and the tool's state-changing nature, the description provides substantial context: it explains the scope of approval, lists applicable contracts, gives real-world use cases, and warns about risks. It could mention that this is an on-chain transaction requiring the owner's signature, but overall it is complete enough for an agent to use it 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 description coverage is 100%, so the schema fully documents all parameters. The description adds some context around the 'contract' enum (ERC-721, ERC-1155, registry) and the meaning of 'approved', but this largely mirrors the schema. It does not introduce new parameter semantics beyond what the schema already provides, so a baseline of 3 is appropriate.

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 opens with a specific verb and resource: "Approve or revoke an operator for ENS contract interactions." It clearly distinguishes this from sibling tools by explicitly naming setApprovalForAll behavior and explaining it covers all tokens, not a single one, which separates it from transfer/wrapping 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?

The description provides concrete common use cases (e.g., "Approve NameWrapper on BaseRegistrar before wrapping a name") that indicate when to use this tool. It does not explicitly name alternative tools or state when not to use, but the context is clear enough for an AI agent to select it appropriately.

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