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

Annotations already cover readOnlyHint and openWorldHint, and the description adds useful auth behavior (anonymous public read, 401 on a wrong key). However it omits the most consequential behavior disclosed in the schema — that supplying a key also mutates the caller's inbox state — and the header-vs-parameter phrasing is ambiguous against a tool whose only param is api_key.

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 with the payload description front-loaded and the auth caveat second; nothing is wasted. Slightly cryptic compression ('omit the authorization header') costs a little clarity.

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 one-optional-param read tool with annotations and no output schema, the description covers what is returned and the auth rule. Gaps remain: 'external items' is undefined, ordering/freshness of 'newest' is unstated, and the key-triggered inbox update is not surfaced.

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 100%, so the baseline is 3. The description adds the 401 failure mode for a bad key, which the schema does not state, but it leaves the inbox-state side effect of supplying api_key unexplained, so net added meaning is modest.

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 the resource and its scope precisely: 'The 20 newest threads and external items', which an agent can distinguish from get_inbox or get_briefing by the words 'threads and external items'. It stops short of naming any sibling it is not, so differentiation is inferred rather than stated.

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 tells the agent how to call it anonymously ('omit the authorization header to call it without a key') but never says when to reach for this over search, get_inbox, or get_briefing. Usage is only implied by the 'newest' framing.

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