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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is settled. The description adds real behavioral context beyond that: the off/draft/send permission semantics, the meaning of 'send' as authorization to act, and the draft fallback when rules are exceeded.

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 trigger ('Call it before writing professionally') is buried mid-paragraph after a long content inventory. The standing-rules instruction is stated twice in near-identical phrasing ('their STANDING RULES in their own words' then 'Follow the person's standing rules ... in their own words'), which is redundant filler in an otherwise dense passage.

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 an output schema present, return values need no explanation, and the description instead supplies the permission model and the draft-when-out-of-bounds rule, which is what an agent actually needs to use the result. It is complete for a zero-parameter read tool, though the entry-point framing could be crisper.

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 input parameters means there is no parameter surface to document, so the baseline of 4 applies. The description's references to 'level' and 'mode: "draft"' describe downstream message behavior rather than inputs to this tool.

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 enumerates what the tool surfaces (professional persona, visibility, headline, public page, permission level, unread professional messages, standing rules) and contrasts it with the person's private life, implicitly distinguishing it from read_profile. It never states an explicit verb like 'retrieve', reading more as a content inventory than an action, which keeps it just short of a 5.

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 gives an explicit trigger — 'Call it before writing professionally' — plus a follow-on behavior (when a message exceeds the standing rules, make it a draft and explain why). It stops short of naming an alternative tool or a when-not-to-use condition, so it misses the top tier.

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