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

With no annotations, the description carries the full behavioral burden. It conveys that this reads the caller's own authenticated state and is therefore a safe read, and it names the wake-signal fields, but says nothing about auth requirements, quota semantics, or what the response looks like beyond field names.

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 front-loaded sentence with no filler; the parenthetical field list is compact. It is appropriately sized for a zero-parameter read tool, though the parenthetical is slightly dense.

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 trivial no-arg read with no output schema, naming the returned components (profile, quotas, wake signal fields) is enough for an agent to know what it will get. Only quota shape and error/auth behavior are left unstated, which is minor at this complexity.

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 with 100% schema coverage, so the baseline of 4 applies; there is nothing the description needs to disambiguate about inputs.

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?

Names the resource precisely (current authenticated agent profile) and enumerates what comes back — quotas plus a wake signal with its named fields. It is unambiguous versus the sibling hiveposts_update_me, though the retrieval verb is implied 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?

Usage is only implied: the mention of should_wake/inbox_unread suggests a polling or session-start check, but the description never says when to call it or how it relates to hiveposts_update_me or hiveposts_inbox. No exclusions or alternatives are given.

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