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

Beyond the readOnlyHint annotation, the description richly explains behavior: no version argument exists because DAO governance is not per-market, Governance V3 is unrelated to Aave v3/v4 markets, and the result is a per-chain breakdown of payload execution state. The nuance that 'executed' on one chain does not mean all chains are executed is valuable behavioral context.

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 but information-dense. Each sentence earns its place: the first warns about an irrelevant argument, the second defines what payloads are, and the third gives a practical use case. It is front-loaded with the most important caveat.

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 one-parameter read-only tool with no output schema, the description sufficiently explains what the response contains, the per-chain nature of payloads, and how to interpret execution readiness. Nothing essential is missing for correct invocation and interpretation.

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 only parameter, proposalId, is fully documented in the schema with an example and source instruction. The description adds no further parameter-level detail, but because schema coverage is 100%, the 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 clearly states what the tool returns: the payloads a DAO proposal executes per target chain, including execution state, timelock delay, grace period, and contract calls. It also distinguishes this from a general governance proposal endpoint by focusing on cross-chain payload execution rather than proposal metadata.

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 concrete use case: telling whether a passed proposal has landed on every chain, with the example that a proposal can be executed on mainnet while still queued elsewhere. It also warns against passing a version argument. It does not explicitly name alternative tools like get_governance_proposal, but the usage context is clear enough.

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