Get Public Timeline

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

Annotations already include readOnlyHint=true, confirming safe read operation. The description adds behavioral context by explaining that 'federated' shows posts from across the fediverse and 'local' only from the instance, clarifying the data scope. No contradictions.

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?

Two sentences, zero waste, front-loaded with the core action. Every sentence adds value—scope clarification is essential. Exemplary conciseness.

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 4 parameters, no output schema, and annotations present, the description covers the main purpose and scope. It does not explain the 'limit' or 'maxId' parameters (though schema covers them). Overall adequate, but could mention default limits for completeness.

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 coverage is 100%, so baseline 3. The description adds meaning beyond schema by explaining the 'scope' parameter options in plain language (federated vs local). It also implies the 'domain' parameter is the instance domain, which is clear.

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 'Fetch an instance's public timeline' with a specific verb and resource. It distinguishes between 'federated' and 'local' scopes, which sets it apart from sibling tools like fetch-timeline or get-home-timeline that may target different feed types.

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 explicitly explains when to use each scope (federated vs local), providing clear context. However, it does not explicitly state when not to use this tool (e.g., if you need a private timeline) or name alternative tools, though the sibling list implies alternatives.

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