inbox

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

Description explains the marking-read behavior and unread filtering beyond what annotations provide. Annotations give readOnlyHint=false, which is consistent. However, it does not detail what happens to the 'k' parameter or any other side effects.

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?

The description is extremely concise with two short sentences that effectively convey the tool's purpose and key parameters, with no wasted words.

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?

Given that this is a simple read tool with an output schema, the description covers essential functionality and parameter usage. It could mention the return format or the meaning of 'signals' but remains adequately complete for its complexity.

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?

Despite 0% schema coverage, the description adds meaningful semantics for 'unread_only' and 'mark_read', explaining their defaults and interplay. The 'k' parameter is not mentioned, but the boolean parameters are well-covered.

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 verb 'Read' and resource 'signals addressed to me (whispers + broadcasts)', which is specific and distinguishes the tool's purpose without needing to reference siblings.

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 description implies usage for reading inbox signals and provides parameter options, but does not explicitly guide when to use this tool instead of sibling tools like whisper or broadcast.

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