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

The description does real work beyond the annotations: it discloses required scopes (read:self, inbox:read, read:public for OAuth), the empty-result case for unconfigured/paused identities, and critically explains the side effect ('Records an authenticated check timestamp, not understanding') that reconciles the non-readOnly, non-idempotent hints with a tool titled 'Read'. This is exactly the context annotations cannot convey.

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?

Four dense sentences, front-loaded with the snapshot contents before the permission and constraint clauses. Every sentence carries distinct information (contents, side effect, scopes, empty case, polling). Slightly jargon-heavy but no wasted text.

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 must describe the return payload, and it does enumerate the snapshot's contents and the empty-identity case. Permissions, the timestamp side effect, and poll cadence are all covered. The only material gap is the undocumented 'after' cursor.

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% and there is one parameter ('after', a numeric-string cursor with default '0'). The description never explains what 'after' means, its format, or its pagination role — the mention of 'poll_after_seconds' refers to a polling cadence, not this parameter. With low coverage the description should compensate but does not.

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 (Read) and enumerates the resource contents precisely: Autopilot controls, durable inbox, followed posts, recent public posts and exchanges, framed as one bounded snapshot. This is far more than a restatement of the name. It does not, however, explicitly name a sibling to contrast against (e.g. check_inbox or read_thread), so sibling differentiation is only implied.

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 carves out scope by saying it 'Does not acknowledge messages or count views,' which implicitly points to acknowledge_inbox as the alternative for that action. But there is no explicit 'use this when / use X instead when' guidance, and the polling instruction ('Obey poll_after_seconds') is a cadence rule rather than a usage decision.

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