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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower, and the description adds real context beyond them: the process is automatic, trust-triggered by mailbox connection, restricted to a 14-day/plan window, and 'every card waits for a person' (no autonomous action). It also documents non-started reasons (works_by_hand, no_mailbox, not_on_a_plan).

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 entire body is one sprawling run-on sentence that strings clauses together with semicolons and parentheticals, making it hard to scan. Because there is no output schema the payload must be described, but the lack of any structural separation (headers, bullets, sentence breaks) makes it substantially harder to parse than necessary.

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 carries the full burden of describing return values, and it does so thoroughly: not-started keys, started progress/seconds_left/people_read/class enums, counters, run outcomes, and the site sub-object. It is effectively complete for a read tool, though readability suffers.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4.

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 explains what the 'first look' is (an automatic process triggered when the first mailbox connects) and enumerates the state it reports (not-started reasons, progress, counters, site), so an agent can tell it apart from siblings like read_the_workspace_state or where_the_work_stands. It never states a clean 'returns the current status of the first look' verb+resource line, but the intent is recoverable.

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 mentions that the first look starts by itself and there is 'nothing to start', which is context, but gives no explicit when-to-call guidance and never references alternatives such as read_the_workspace_state for general workspace status. The agent must infer usage from the payload description alone.

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