x_notifications

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

The description explicitly discloses the side effect that visiting the page can mark notifications as seen, which explains the readOnlyHint=false annotation. This adds valuable context beyond the annotations and warns the agent about state mutation.

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 concise sentences with the primary purpose front-loaded and the side effect stated immediately afterward. Every sentence contributes meaningful information with no redundancy.

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?

The core purpose and important side effect are covered, and the return shape is hinted at, but the behavior of maxScrolls and how 'visible' notifications are determined remains underspecified. For a simple optional-parameter tool this is acceptable but not complete.

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 0%, so the description carries the burden of explaining parameters, but it does not mention tab, limit, or maxScrolls at all. The enum and bounds in the schema give some clues, but the description adds no parameter-level meaning.

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 clearly states the tool reads visible notifications/mentions and returns text, links, and timestamps. This is specific enough to distinguish it from the sibling tools, though it does not explicitly name an alternative or contrasting tool.

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 the tool should be used to read notifications or mentions, but it provides no explicit guidance on when to use it over sibling tools like x_timeline or x_search. There are no exclusion criteria or alternative routing instructions.

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