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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds non-redundant context by explicitly scoping the tool to a public registry view and warning that write/disposition paths are absent — which also resolves the ambiguity created by the title ('Retrieve or acknowledge'). It still says nothing about what a Founder Signal contains.

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 sentences, front-loaded with the actual operation, with no filler. Slightly under-specified rather than over-long; nothing to trim.

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?

Adequate for a single-operation read tool with an enum-constrained required parameter and no output schema. However, with three trailing parameters that look writable but are inert, a caller would benefit from one line confirming that only `operation: get_latest` is meaningful.

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 100%, so baseline is 3. The description's note that disposition writes are unavailable implicitly explains why reason, message_id, and idempotency_key exist but do nothing here — useful, yet it never says this directly about the parameters, so no credit above baseline.

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 concrete verb and resource: read the latest publicly available Founder Signal. It is clear enough to act on, but it does not differentiate from any named sibling (all siblings cover unrelated Cassie-domain resources), so it stops short of a 5.

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 second sentence establishes when this tool applies (read-only access to the public registry) and when it does not (disposition writes are unavailable through this schema). No alternatives are named, and the caller is not told what to do if they actually need a disposition.

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