truth_home_timeline

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

Annotations already readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds the scoping to the authorized account, which is useful, but it does not disclose pagination behavior or response format (though an output schema exists). No contradiction with annotations.

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 a single concise sentence with zero filler. It front-loads the action ('Fetch') and resource, achieving maximum clarity with minimal words.

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?

As a simple read tool with rich annotations and an output schema, the description covers the essential purpose. However, it lacks parameter explanations and explicit usage guidance, so it is not fully complete for an agent without prior knowledge of timeline pagination.

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 description does not explain limit, max_id, or since_id. While param names are somewhat self-evident and constraints exist, the description fails to compensate for the lack of schema-level documentation, leaving pagination semantics unclear.

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 uses a specific verb and resource: 'Fetch the authorized account's home timeline.' It clearly distinguishes from siblings like truth_get_status (fetch a single status) or truth_get_user_posts (fetch a user's posts), making the tool's unique scope apparent.

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 states the resource clearly (home timeline of authorized account) but does not provide explicit guidance on when to use this tool versus alternatives like truth_search or truth_get_user_posts. Usage is more implied than explicitly contrasted with siblings.

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