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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral fact beyond that: it does not mark alerts retrieved, clarifying a side effect an agent might otherwise assume. Return-shape detail (pagination, size) is absent but not critical here.

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?

A single dense sentence that front-loads the highest-value content (pending alerts, top items) before less central items, followed by a short side-effect disclaimer. Every clause maps to a distinct part of the digest, though the sentence is long enough to be slightly taxing.

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 carries the burden of describing what comes back, and its enumeration of digest sections does this well. Personalization is stated ('learned-preference suggestions'), so an agent understands the result is user-specific. Minor gaps remain around freshness/refresh behavior but nothing essential is missing.

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 takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it correctly spends no space on parameter semantics.

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 names a specific resource (a personalized digest) and enumerates its contents: pending alert counts, watchlist matches and data age, tracked property changes, and preference suggestions. This clearly separates it from narrower siblings like get_property_alerts or get_property_history, though it does not explicitly name those alternatives.

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?

Usage is implied (a digest is the natural starting point for a session) but there is no explicit when-to-use or when-to-prefer-alternatives guidance. The clause 'Does not mark alerts retrieved' is the only comparative hint, implicitly contrasting it with alert-fetching tools that may change state.

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