dashclaw_inbox_list

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

No annotations provided; description mentions output fields (is_read flag, unread_count) but does not disclose ordering, pagination, side effects, or rate limits. For a list tool, minimally transparent.

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: purpose, usage guidance, output details. Front-loaded, no redundancy, every sentence contributes.

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 5 optional parameters and no output schema, the description covers the return shape and common use cases. Lacks pagination or ordering details, but sufficient for typical use.

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%, but description adds value by explaining the output (is_read flag, unread_count) and usage pairing. This goes beyond the schema's parameter descriptions.

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?

Clearly states 'List this agent's DashClaw inbox messages and unread count' – specific verb+resource. Distinguishes from sibling tools like dashclaw_messages_mark_read by mentioning pairing.

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?

Explicit when to use: 'at the start of a session, or when notified...before deciding what to do next.' Also suggests pairing with dashclaw_messages_mark_read, though no explicit when-not or alternative tools.

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