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

With no annotations, the description must carry the behavioral burden. It discloses that the tool returns ~value and implies a pure, read-only computation. However, it omits important behavioral details such as integer width, signedness, JavaScript's 32-bit signed integer coercion semantics, and how invalid or non-integer inputs are handled.

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 compact, front-loaded with the operation name, and each sentence earns its place: one states the operation, and one states the input and return behavior. There is no 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?

The tool is simple, but no output schema and no annotations mean the description is the sole contract. It fails to specify how the value is passed given the empty schema, and it lacks precision about integer representation and edge cases. An agent cannot reliably construct a correct invocation from this definition alone.

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 input schema is empty, yet the description instructs the agent to 'Provide value'. No property named 'value' is defined in the schema, and no type or format is specified. The ~value formula adds semantic meaning, but the missing parameter slot creates a genuine invocation gap.

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 uses a specific verb and resource: 'Perform a bitwise NOT operation on an integer' and gives the exact return formula 'bitwise complement (~value)'. This clearly distinguishes it from siblings like x402-bit-and, x402-bit-or, and x402-bit-xor.

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 operation is clear, so when to use it is implied: use it when a bitwise complement is needed. However, there is no explicit guidance about when not to use it or which sibling alternatives might be more appropriate, such as bit-toggle or bit-xor.

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