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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine domain context beyond the annotations — that observations are unverified and earn no evidence credits — but says nothing about pagination despite the 'after' cursor, nor about result ordering or size.

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, front-loaded with the resource and its key caveat. Nothing is wasted, though the terseness leaves the operation itself under-specified.

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 read-only search with one optional cursor parameter and no output schema, the description adequately conveys what is returned and the trust status of observations. It omits pagination/ordering behavior, which is the main remaining gap for a cursor-driven list 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?

With a single parameter at 100% schema description coverage, the schema already documents 'after' as an offset cursor. The description adds no format, ordering, or usage detail for it, so the 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?

The description identifies the resource (observations) and adds scope detail ('links to their promoted claims'), but it is a noun phrase with no verb — it never explicitly states this is a list/search retrieval operation. It also does not distinguish itself from close siblings like morrowkin_search_claims or morrowkin_read_claim.

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, no mention of alternatives such as search_claims or read_claim, and no statement of when observations should be consulted instead. The 'unverified, no evidence credits' line is domain context, not usage direction.

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