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

No annotations are provided, so the description carries the burden. It discloses that it only builds calldata (not executes) and mentions the 'payable' condition for actions with ETH value. However, it does not explicitly state that calling this tool has no side effects or what the return value is, leaving some ambiguity.

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?

One sentence, front-loaded with the action, then the condition. No unnecessary words; every word earns its place.

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 single-parameter builder tool, the description covers the key prerequisites and behavior. But with no output schema, it omits what the function returns (e.g., calldata hex string) and whether it submits the transaction. It is adequate but not fully complete.

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 schema fully describes proposalId with type and bounds, so baseline is 3. The description adds meaningful context: the proposal must be queued and past the timelock, and that it is used in the execute function. This enhances understanding of how to provide the parameter.

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 'Build' and resource 'execute(proposalId) calldata' for a 'Queued Jestermogger proposal,' clearly distinguishing it from siblings like build_queue_tx or build_veto_tx. The purpose is unambiguous.

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?

It specifies the exact precondition—'past its 2-day timelock' and 'Queued'—which tells the agent when to use this tool. However, it does not explicitly name alternative tools or state when not to use it, so it falls just short of the highest bar.

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