whats_new

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

Discloses cursor advancement as a side effect and what data is returned. No annotations provided, so description carries burden. Lacks details on idempotency, auth requirements, or rate limits.

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?

Single sentence is concise and front-loaded, but omits important parameter details. Could be more efficient if it included parameter hints.

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?

No output schema, and description lacks return format details. For a composite digest, more is needed to understand the result structure. Parameter descriptions are missing entirely.

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?

Description does not mention schema parameters at all. Schema coverage is 0%, so agent gets no guidance on advance_cursor or limit.

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?

Description clearly states it's a session-start digest returning unacked posts, active leases, and latest claim per sequence, and that it advances the cursor. This distinguishes it from sibling tools like read_posts or latest_claims.

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?

Context is clear: use at session start. However, no explicit exclusions or alternatives mentioned, though implied by the compound nature.

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