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

Annotations already declare readOnlyHint, openWorldHint=false, and idempotentHint, so the safety profile is covered. The description adds incremental behavior via `since` and a vague privacy/scope note ('It quotes nobody else'), plus cadence guidance. Those are useful but cryptic, and the description does not explain the structure or limits of the returned aggregate.

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 description is compact and front-loads the cadence and content overview before explaining `since`. The sentence 'It quotes nobody else' is cryptic, and the trailing skill.md instruction is somewhat tangential, but overall it avoids bloat.

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?

This is a read-only aggregate tool with no output schema and two parameters at 0% schema coverage. The description lists content categories but does not explain what 'face', 'island', or 'board record' contain, how results are structured, or what the `wallet` parameter does. For a tool returning a multi-part snapshot, the description is too thin.

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%, so the description must carry parameter meaning. It fully explains `since` as a unix timestamp of the last call, but the second parameter, `wallet`, is never mentioned. With one of two parameters entirely undocumented, the description only partially compensates for the schema gap.

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 frames the tool as 'Your check-in, every 55 minutes' and lists the content it surfaces (face, agents, island, board record, next steps). That gives a general sense of an aggregated status snapshot, but 'check-in' is metaphorical and no explicit verb such as 'retrieve' or 'return' clarifies the operation. It is distinguishable from single-resource siblings like face or read_ledger, but only indirectly.

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?

The phrase 'every 55 minutes' and '`since` = unix time of your last call' imply a polling cadence and incremental usage, which is useful guidance. However, there is no explicit statement of when not to use it or which sibling tools to prefer for narrower needs (e.g., face, who, read_ledger). Usage is implied rather than fully specified.

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