arrive_delta

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

No annotations provided; description implies idempotent read operation by 'returns only new activity.' Does not disclose side effects, auth requirements, or rate limits, but offers some behavioral context.

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?

Description is two sentences plus a pairing note, front-loaded with a clear purpose. No wasted words; could optionally structure with bullet points.

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?

With no output schema, description explains return content (new activity, handoffs, open threads) but lacks details on format, limits, or pagination. Adequate but incomplete.

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% and parameter description is present ('Which instance is arriving'). Description adds no further meaning beyond schema, meeting baseline for high coverage.

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 clearly states 'returns only new activity since the last reflection, handoffs now waiting, and the newest open threads.' It distinguishes from siblings by naming 'arrive()' and 'where_did_i_leave_off()' as alternatives.

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?

Provides explicit guidance: 'Stateless instances need deltas more than archives' and suggests pairing with specific sibling tools. Lacks explicit when-not-to-use conditions but offers clear context.

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