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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered externally. The only behavioral addition is the vague phrase 'without deterministic outcome claims,' which hints at an output-epistemics policy but never specifies it.

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?

It is short, but the single sentence is almost a pure restatement of the name and title, so it spends its words on redundancy rather than front-loading any actionable information.

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 10-parameter tool with a complex conditional schema (place OR lat/long/timezone) and low description coverage, the description supplies none of the missing context about inputs or behavior. Even with an output schema present, this is far too thin.

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 10 parameters and only 30% schema description coverage, the description carries the burden of explaining the many undocumented inputs, yet it mentions none of them (name, date, time, topics, asOfIso, etc.). It adds zero meaning beyond the schema.

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 restates the tool name almost verbatim ('build claim evidence ledger'), adding only the qualifier 'without deterministic outcome claims.' It never states what a 'claim evidence ledger' actually does or what input it consumes, so it is effectively tautological with the title.

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 differentiation from the many sibling analysis/audit tools (audit_prediction_claim, audit_reading_evidence, assess_prediction_readiness). An agent cannot infer from this text when this tool should be chosen over those.

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