Get Simulation Posts

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the safety profile is well established. The description adds context about the content type (agent-generated, Twitter/Reddit style) but does not disclose any additional behavioral traits such as pagination, sorting, or volume limits. This is acceptable given the strong annotations, but the added value is moderate.

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, front-loaded sentence that immediately communicates the tool's purpose without any filler. Every word adds value, making it exemplary in 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?

For a read-only tool with a single fully-documented parameter and no output schema, the description adequately explains what the tool returns (social media posts) and the context (agent-generated simulation posts). It lacks explicit sibling differentiation but is otherwise complete for the tool's simplicity.

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?

The only parameter, simulation_id, is fully described in the schema ('The simulation ID'), achieving 100% schema description coverage. The description text does not add any further parameter-specific details, so the baseline score of 3 is appropriate.

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 tool's function with a specific verb ('Get') and resource ('social media posts'), further qualified by 'generated by agents during the simulation' and '(Twitter/Reddit style)'. This effectively distinguishes it from sibling tools like get_simulation_comments or get_simulation_actions.

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?

No explicit usage guidance is provided. The description does not mention when to use this tool versus alternatives, nor does it offer any exclusions or contrasting sibling tools. Given the large set of similar simulation-related read tools, this lack of differentiation is a clear gap.

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