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

No annotations are provided, so the description carries the burden and does so well: it declares 'Nothing is sent or changed by calling it' (read-only safety), discloses newest-first ordering, cursor pagination, and the retention-window caveat where target names may be erased. Missing only things like rate limits or result-size ceilings.

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?

Front-loaded with purpose and safety before the usage triggers and arg docs; every section serves a purpose. The quoted example queries add real routing value, though the entry-field enumeration borders on verbose.

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?

Despite no output schema and no annotations, the description specifies the returned entry fields (at, action, surface, status, target, summary, detail, error) and the pagination contract via next_cursor. An agent has everything needed to call it and interpret results.

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 the schema has no enums, yet the description documents every parameter: limit (1-100, default 20), cursor (next_cursor from prior call), surface values ('linkedin'/'iridium', omit for both), status values ('success'/'failed'/'skipped'), and action_type as an exact slug with an example. This fully 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?

States a specific verb and resource ('Read the user's activity log'), its scope ('Every action Iridium has taken, newest first'), and its backing store (append-only ledger). An agent can immediately distinguish it from narrow siblings like get_last_action.

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?

Gives explicit trigger conditions with concrete example queries ('what did you do today?', 'what failed?') and a strong directive to answer from the log rather than conversation memory. It does not name alternatives such as get_last_action for single-action lookups, so no exclusion guidance exists.

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