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

The description explicitly claims 'Read-shaped tools only' and that anything that buys, sells or writes refuses, implying the tool is read-only. The annotations declare readOnlyHint=false, which contradicts that claim. This is a serious inconsistency. The description otherwise adds useful context about the MCP-only nature and data passthrough.

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 core purpose is front-loaded in the first sentence, but later sentences mix useful behavioral notes with marketing-style phrasing and a listing URL that do not aid tool invocation. It is reasonably short but not fully tight.

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 and six parameters, the description leaves important gaps: the return format, the interaction between name/handle/following, and what 'data comes back as it is' means for the caller. An agent would need external knowledge to invoke it confidently.

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 only 33% (2 of 6 parameters documented), so the description must compensate. It clarifies scope values and mentions authCode, but name, handle, limit, and following remain unexplained in both the schema and the description.

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 opens with a specific verb and resource: 'Read the Life Agent timeline' and enumerates the three scopes (global feed, one profile, or following). This clearly distinguishes it from sibling Orbitx tools like life_account or life_files.

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 text provides some usage context by stating this is read-shaped and that anything buying, selling, or writing refuses. However, it does not explicitly say when to choose this over sibling timeline-related tools or how the scope modes map to concrete scenarios.

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