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

With no annotations, the description carries the full behavioral burden, but it discloses useful context: this is a GET endpoint, requires a logged-in resident, and can serve as an auth probe before create_guest_invite. It does not describe read-only safety, pagination, failure behavior, or response shape, leaving meaningful gaps for a fetch tool with no annotation coverage.

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 and front-loads the resource and scope, then supplies use cases and an operational cue. The trailing reference to 'GET /notification (steps 1, 2, 15)' is terse and somewhat opaque, but it does not waste space or bury the main purpose.

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 fetch tool with one optional parameter, no output schema, and no annotations, the description provides enough context to select and invoke it: purpose, scope, usage examples, and an auth-probe ordering note. It could be stronger with a note on pagination or return behavior, but the core is 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?

There is one optional parameter with 100% schema description coverage, so the schema already defines notification_message. The description adds no meaning about this parameter or its role in a fetch operation, which is the baseline expectation when schema coverage is high.

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 identifies the resource as a notifications feed for the logged-in resident and specifies it includes past guest invites with names, codes, and times. It does not explicitly contrast with similar siblings like fetch_guest_invite_advertisements, but the scope and contents are concrete enough for an agent to understand what it returns.

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?

It lists explicit use cases—notifications, invite history, guest-invite activity, checking history—and adds a valuable ordering cue: use as an auth probe before create_guest_invite. It does not state when not to use it or name alternative tools for overlapping needs, so it stops short of the top score.

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