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

The description goes well beyond the readOnly/destructive annotations by disclosing that timeouts are explicit failures, that the enabled state depends on whether AXEnabled is published, and that a missing AXEnabled produces enabled_unknown:true. This gives an agent crucial behavioral nuance that annotations alone cannot convey.

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 dense but every sentence earns its place: it states the primary purpose, the timeout contract, the return shape, and a subtle behavior around AXEnabled. The key phrase 'replaces all sleeps' is front-loaded, and 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?

For an 8-parameter polling tool with no output schema, the description is unusually complete: it specifies the return object shape, what happens on timeout, and how ambiguous enabled states are represented. The schema covers the parameters, and the description covers runtime behavior adequately.

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 coverage is 100%, so each parameter is already documented. The description adds extra meaning around the state parameter's enabled semantics and the timeout parameter's failure semantics, which the schema does not fully express. This exceeds the baseline without duplicating field docs.

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 names a specific verb ('polls') and resource (an element), and defines the outcome as reaching a target state or timing out. It also differentiates itself from ad-hoc sleeps by calling itself 'deterministic synchronization,' making its role clear next to siblings like web_wait_for.

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 opening 'replaces all sleeps' establishes a clear usage context, and the timeout behavior clarifies a key expectation when using the tool. It does not explicitly enumerate alternatives or when-not-to-use scenarios, but the intended role as the synchronization primitive is clear.

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