Your notifications

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds minimal context by specifying 'recent' and 'on your account,' but it does not disclose behavioral traits like result limits, read-state effects, or pagination, so it adds only modest value beyond annotations.

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 a single short sentence with no redundant words. It is appropriately sized for a simple read-only tool and delivers the core message efficiently.

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, the description should compensate by explaining what the response contains (e.g., list of notifications, fields like message and timestamp). 'Recent notifications on your account' is too vague to convey the data shape or any behavioral details, leaving the agent under-informed.

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 tool has zero parameters, and the input schema contains no properties. With no parameters to document, the description need not explain syntax or meaning; the baseline of 4 for 0-parameter tools applies.

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 'Recent notifications on your account' clearly identifies the resource (notifications) and scope (user's account), making the tool's purpose understandable. While the verb is implied rather than explicit, the name 'get_notifications' reinforces the retrieval action, and there are no sibling tools for it to be confused with.

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 provides no guidance on when to use this tool, what conditions warrant it, or how it differs from alternatives. It merely states what it returns, leaving the agent without contextual cues for selection or exclusion.

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