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

The description adds genuine behavior beyond the readOnlyHint/openWorldHint annotations: results are tiered by participation, with participants receiving a hash-chained log plus verification and non-participants receiving only status transitions. That is meaningful, non-obvious disclosure. It stops short of covering ordering, volume, or pagination for what could be a large log.

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?

Two short sentences with zero filler, and the access-tier behavior is front-loaded right after the topic. The opening fragment is cryptic on its own, which is the only structural weakness.

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 single-parameter read tool with no output schema, the description does the important work of explaining what is returned and why it differs by caller. However, with no output schema to fall back on, the absence of any detail on log shape, ordering, or size limits leaves an agent under-informed for parsing the response.

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?

With one parameter at 100% schema description coverage, the schema already defines task_id and its tsk_... format. The description adds nothing about it, so baseline 3 applies.

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?

"Event history" identifies the resource but is a bare noun fragment with no verb and no explicit statement that it retrieves a task's event log; the agent must lean on the tool name to confirm. It does not distinguish itself from siblings like get_task or get_proof, which plausibly return overlapping data.

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?

There is no when-to-use guidance and no named alternative, even though get_task, get_proof, and list_deliverables are obvious candidates for adjacent information. The only routing signal is the implicit access-tier distinction, which an agent cannot act on before calling.

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