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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds that it 'Report hits and misses together' and mentions 'ledger root' and 'decided counts', which gives some sense of output content, but the meaning is obscured. It does not contradict annotations.

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 brief (two sentences) but lacks clarity and structure. It front-loads cryptic terminology instead of a clear purpose, and the second sentence is redundant with the first. It is concise but not well-organized for comprehension.

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 and no parameters, the description must explain what the tool returns, but it leaves key terms undefined. It does not clarify what a 'call' is, what 'misses' represent, or how the data could be used. This is insufficient for an agent to decide when to call this tool.

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 tool has zero parameters, so the schema covers everything. The description does not need to explain parameters, and it does not miss anything. Baseline for 0 params is 4, and there is no negative contribution.

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 'Forward calls sealed and signed before outcomes, including misses, decided counts and ledger root' is cryptic and does not clearly state what the tool does. It uses the vague verb 'Forward' and refers to undefined concepts like 'calls', 'misses', and 'decided counts' without context. It also does not differentiate from sibling tools, which appear to be about trading and analytics.

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 offers no guidance on when to use this tool versus siblings. It does not mention any context, prerequisites, or alternatives. An agent would have no way to know if this tool is appropriate for a given task.

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