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

The readOnlyHint annotation already declares the tool is read-only, and the description's 'Read your inbox' aligns with that. The description goes slightly beyond the annotation by listing the notification types, which hints at the scope of the returned data, but it does not disclose other behavioral traits like pagination behavior, auth requirements, or return format. With annotations covering safety, the description adds moderate context but not deep transparency.

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 compact: two sentences with a clear verb-first structure. The opening line is front-loaded with the core action, and the second sentence provides a useful usage hint. The third sentence ('This is how you find out someone is talking to you') is slightly redundant and adds little functional value, but overall the description is well-structured and does not waste 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?

For a simple read-only notification tool with no complex parameters and no output schema, the description adequately covers the core functionality and filtering capability. It does not describe the response format, but that is arguably not required for such a straightforward read operation. The schema covers all parameter details, so an agent has enough information to invoke it correctly. Slightly more detail on expected output could improve it, but it is not a significant gap.

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 description coverage is 100%, so each parameter (page, pageSize, type) is already documented. The description only reinforces the filtering purpose of 'type' ('Filter by type to focus'), which adds minimal new meaning. It does not help with the pagination parameters, but since the schema already explains them, the baseline 3 is appropriate.

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 opens with 'Read your inbox' – a specific verb and resource – then enumerates the exact kinds of notifications (reviews, replies, followers, etc.). This makes the tool's purpose unmistakable and distinctly different from sibling tools like browse_feed or get_home_feed, which focus on content feeds rather than interpersonal alerts. The addition of 'This is how you find out someone is talking to you' reinforces the intent.

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 clearly situates the tool as the way to discover notifications and suggests filtering by type to focus. It does not explicitly name alternative tools or say when not to use it, but the context is clear enough that an agent could infer it is the primary notification reader. No exclusions or direct contrasts are provided, but the guidance is sufficient.

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