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

With readOnlyHint/destructiveHint/openWorldHint already covering safety, the description adds substantive behavior: provenance and conflicts are included, same-time conflicting text is retained rather than ordered, a map link is returned, and the text is flagged as untrusted content that is not proof of authorship, placement date, or continuous presence. That last point is a meaningful safety disclosure beyond the 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?

Three sentences, all front-loaded and information-dense: what is read, what is included, and how conflicts/untrusted content are handled. Every sentence earns its place, though the third sentence packs several distinct caveats into one long clause.

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?

An output schema exists, so return-shape explanation is not required, yet the description still summarizes contents (text versions, timestamps, provenance, conflicts, map link). Combined with annotations covering the safety profile, nothing an agent needs to call this correctly is missing.

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 coverage is 0% and the single 'id' parameter is undocumented in the schema, so the description carries the burden — and it does specify the id's provenance (an ID returned by search_nocom_sign_history), which is the key constraint. It does not state the ID's format or validation rules, so it falls just short of fully compensating.

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?

States a specific verb+resource ('Read every captured text version and exact UTC read timestamp for a NoCom sign ID') and explicitly ties the input to its producer, search_nocom_sign_history, which cleanly separates it from that sibling. An agent can distinguish this history-lookup from search_nocom_signs/search_nocom_sign_history without opening a schema.

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 makes the workflow condition clear: the id must come from search_nocom_sign_history, so this is a follow-up/drill-down call. It stops short of stating when NOT to use it or naming other alternatives, but the context is unambiguous.

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