read_social_results

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

With no annotations, the description carries full weight. It discloses the 409 error for incomplete runs, the pagination loop with meta.next_cursor, and the filter/order capabilities. It does not cover authentication or rate limits, but for a read operation this is adequate.

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?

Three well-organized sentences: purpose, error/filtering, pagination/alternative. No wasted words, front-loaded with the main verb and resource.

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?

Given the complexity (8 params) but presence of output schema and 100% schema coverage, the description sufficiently covers key behaviors—error condition, pagination, and tool selection. It could mention the token origin, but schema already states it comes from start_run.

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 is 3. The description adds value by specifying the pagination loop ('Pass cursor until meta.next_cursor is null') and clarifying the sorting/filtering usage, which goes beyond individual schema descriptions.

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 'Fetches the individual social posts of a completed run, with metrics' — a specific verb and resource. It also distinguishes itself from the sibling tool by stating 'use read_result_summary for the big picture,' making its purpose unambiguous.

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 explicitly states when to use this tool: 'Use this for post-level detail' and contrasts with read_result_summary. It also notes the run must be complete (409 otherwise) and provides pagination instructions, giving clear context.

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