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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add genuinely new scope information — that only metadata/approved fields are returned and that secrets, contacts and original files are excluded — which is a useful data-exposure constraint. It says nothing about permission scoping ('authorised' is never explained), result ordering, or pagination caps implied by offset's 25000 maximum.

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 short sentences with the read scope front-loaded, so it is not bloated. However, the clause 'through the existing application' consumes a third of the text without conveying anything actionable.

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 and 0% parameter documentation, the description should carry more weight than it does. It does disclose the data-exposure boundary, which is the most important ambiguous aspect of a notification listing tool, but leaves the query/filtering behavior and result shape entirely unexplained for a three-parameter tool.

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 all three parameters (limit, query, offset) carry no documented meaning anywhere. The description makes no attempt to compensate — it never says what 'query' searches over (subject? body? sender?) or that limit/offset are pagination controls, which is the main thing an agent needs to call this correctly.

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 verb 'Read' plus resource 'notifications' gives a workable purpose, but 'through the existing application' is a vague qualifier that adds no discriminating information. It also does not distinguish this list tool from the numerous notification-preference siblings (get_notification_digest_preferences, get_organization_notification_preferences, get_employee_notification_defaults).

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?

There is no statement of when to use this tool, when not to, or which sibling it replaces. With a crowded namespace of notification-related getters, an agent is left to infer that this returns notification records while the get_* siblings return preferences, and nothing in the description confirms or denies that.

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