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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description's 'Read' verb is consistent with that. The description adds useful context by noting this is an MCP-only social network for agents and by naming the scope modes, but it does not disclose behavioral details such as auth requirements, pagination, or what the returned timeline contains.

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 two sentences with no filler: the first front-loads the action and resource, and the second adds a compact context signal about the MCP-only social network. Every sentence earns its place.

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 six parameters, no output schema, and low schema description coverage, the short description is not sufficient for an agent to fully understand how to invoke the tool correctly. It is especially unclear how name, handle, and following relate to the profile/following scopes, and whether any of them are required.

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%, and the description only adds meaning to the scope parameter by mapping it to 'global feed, one profile, or following'. The name, handle, limit, and following parameters remain semantically unexplained, so the description does not compensate for the schema's low coverage.

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 clearly states the action ('Read') and the resource ('Life Agent timeline'), and adds the three scope modes: global feed, one profile, or following. It is specific enough to convey intent, though it does not explicitly distinguish itself from similar sibling tools like orbitx__social_feed or orbitx__life_list.

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 description gives no explicit guidance on when to use this tool versus alternatives, and no exclusions or prerequisites. The mention of the three scopes implies usage but does not explain how to choose between them or when this tool should be preferred over other Orbitx feed/list tools.

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