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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing that no state is broadcast, that results are predictions of gas and balance changes, and that the tool works without an API key subject to per-client rate limits unless the operator disables public simulation. It does not cover failure behavior or what happens if the simulation reverts.

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?

Three short sentences, front-loaded with the core action and scope, then returns, then environmental constraints. No filler or repetition.

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?

With no output schema, describing the predicted gas and balance changes is useful, and the rate-limit/prerequisite note is valuable context. But a five-parameter simulation tool with zero parameter documentation — including a USD drain cap that an agent must set correctly — leaves real gaps.

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 0% across five parameters, so the description carries the full burden — and it provides no parameter information at all. Non-obvious inputs such as maxAllowedDrainUSD and the wei-denominated valueWei are left entirely unexplained.

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?

States a specific verb and resource ('Simulates a transaction on Tenderly') and immediately contrasts with execution ('without broadcasting'), which implicitly separates it from the sibling execute_onchain_intent. It never names that sibling explicitly, so the differentiation requires a small inference.

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 phrase 'without broadcasting' implies this is the pre-flight/validation step, but the description never says when to call it versus execute_onchain_intent or get_smart_account_info. Usage is inferable rather than stated.

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