m2m_get_gas_metrics

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does communicate that this is a read-only 'Return' operation and adds useful context with 'sourced' and 'execution recommendations.' However, it does not clarify what execution recommendations mean, data freshness, or any caveats about the response.

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 a single sentence with no wasted words; 'sourced' and 'execution recommendations' add meaningful specificity. It is well-structured and front-loaded, though it could have been expanded with sibling differentiation without becoming verbose.

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 zero-parameter tool, the description is mostly adequate and tells the agent what the tool returns. However, because there is no output schema, the description should explain more about the shape of the response and what 'execution recommendations' actually are. It also leaves the relationship to get_gas_fees unexplained.

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 has no parameters and schema description coverage is effectively 100% because the schema is empty. With zero parameters, the description does not need to document parameter semantics, so the baseline of 4 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 states a concrete action ('Return') and a specific resource ('sourced Base gas fee metrics and execution recommendations'), so it is not a tautology and clearly indicates what the tool does. However, it does not explicitly distinguish itself from the sibling tool get_gas_fees, leaving some ambiguity about how it differs.

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 no guidance on when to use this tool versus alternatives such as get_gas_fees or m2m_get_token_price. It does not mention any conditions, exclusions, or scenarios where a different tool should be preferred, so an agent has no explicit routing information.

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