missed_summary

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

With no annotations, the description carries the behavioral burden and does disclose useful traits: OTP codes are excluded and the default window is 60 minutes. However, it does not state read-only status, auth requirements, or whether the summary returns counts versus message details.

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 compact clauses with no filler; the purpose and key constraints are front-loaded. The fragmentary phrasing is efficient rather than confusing.

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?

For a simple summary tool with one optional parameter and an output schema, the description covers the channels, OTP exclusion, and default window. It omits explicit read-only/auth context and sibling routing guidance, but nothing critical for correct invocation is missing.

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?

The sole parameter 'minutes' has 0% schema description coverage, so the description must compensate. It supplies both the default value and the timeframe meaning via 'Default last 60 minutes,' which is sufficient for this single optional parameter.

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 the resource and scope clearly: recent phone arrivals across WhatsApp, mail, SMS, and OTPs. The channel list differentiates it from single-channel siblings like last_whatsapp and latest_otp, though the phrasing lacks an explicit verb.

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 the default lookback window ('Default last 60 minutes') but does not explicitly say when to choose this multi-channel summary over sibling tools such as last_whatsapp or latest_otp. Usage is implied by the channel list rather than guided with alternatives or exclusions.

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