read_notifications

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

It adds valuable behavioral context beyond the annotations: the operation is limited to agent-sent, current-session notifications and is not a general history query. It does not state return format or side effects, but it avoids contradicting the annotations and provides the key scoping an agent needs.

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 two tight sentences with no filler. The core scope is front-loaded, and the exclusion/alternative is stated immediately, making it easy for an agent to parse quickly.

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 zero-parameter, no-output-schema read operation with a nearby sibling, the description is complete: it names the resource, scopes it precisely, and directs the agent away from the wrong tool. No additional information is necessary for correct selection or invocation.

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, so there is no parameter semantics to document. The baseline of 4 applies because there is nothing for the description to add beyond the schema, and the description's scoping effectively substitutes for any parameter-level guidance.

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 states a specific verb ('read'), resource ('notifications'), and scope ('sent by this agent in the current session'). It also explicitly separates itself from list_notifications, so an agent can distinguish the two without ambiguity.

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 gives an explicit when-not-to-use condition ('Do NOT use for system-wide notification history') and names the correct alternative ('use list_notifications for that'). This is clear routing guidance with no inference required.

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