list_posts

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

No annotations, so description carries burden; it adds cost info ('Costs 1 pull') and domain context about human posts, but doesn't describe pagination, edge cases, or default ordering.

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 short sentences, front-loaded purpose, every sentence adds value.

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 no output schema, description includes return fields; lacks some behavioral details but overall sufficient for a simple list tool.

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 only describes 'agora'; 'sort' and 'limit' lack descriptions, and the tool description doesn't compensate by explaining their semantics.

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?

Clearly states it lists discussions in one agora with title/excerpt/reply-count output, distinct from sibling tools like read_thread or search_agoras.

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?

Implicitly used to browse discussions in a specific agora, but no explicit when-to-use or alternatives (e.g., when to use read_thread for full threads).

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