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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered structurally. The description adds genuinely new context: the setting defaults to off and why (incoming messages are foreign text entering the agent's context), which matters for interpreting the result. It stops short of describing the response envelope.

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, front-loaded with the return value, then the default and its rationale. No filler, and the sibling pointer is placed last where it is most useful.

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 no-param read with rich annotations and no output schema, the description covers what is returned, the default state, and where to change it. It leaves slight ambiguity about the exact response shape (whether only `accept_from_other_users` is returned or additional preference fields accompany it).

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?

Zero parameters, so there is nothing to disambiguate; baseline is 4. The description correctly frames the call as scoped to 'this user's agents' with no identifiers needed.

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?

States a specific verb and resource (return the `accept_from_other_users` messaging preference) and names the exact flag returned. It also implicitly separates itself from the setter sibling `messaging_preferences`, so an agent can pick the right tool without opening a schema.

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?

Points at the alternative that matters — `messaging_preferences` is the tool that changes this value — which gives clear read-vs-write routing. It does not spell out explicit when-not conditions (e.g. whose preferences can be read), so it falls just short of a 5.

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