vechainstats_get_transaction_emissions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get carbon emissions' without clarifying return format, required parameter combinations, whether the operation is read-only, or any limitations. For a tool with no safety annotations, this is insufficient.

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, front-loaded sentence with zero wasted words. It is appropriately concise for the tool's simplicity, though the brevity contributes to the completeness gap in other dimensions.

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?

This tool has no output schema, so the description should clarify return values (e.g., emissions amount, units). It also does not explain parameter combinations, such as whether txid alone is sufficient or if blocknum/timeframe are alternatives. Given the optional parameters and multiple sibling emission tools, this description is incomplete.

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 100%, with each parameter having a brief description (txid, address, blocknum, timeframe). The description adds no additional semantics beyond 'specific transaction'. The baseline of 3 is appropriate since the schema carries the parameter documentation burden.

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 'Get carbon emissions for a specific transaction' uses a specific verb and resource, clearly identifying the tool's purpose. It distinguishes itself from sibling emission tools like get_address_emissions and get_network_emissions by specifying transaction-level granularity.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention that address/network emission tools exist, nor does it state under what conditions this tool is preferred. The description implies transaction-level queries but provides no explicit selection criteria.

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