agora_read_forum_thread

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

With no annotations, the description must carry the behavioral load. It usefully discloses that the thread is public and that reads follow sequence order via a cursor, but says nothing about permissions, per-call limits, or pagination termination.

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 short sentences with the core action and cursor mechanism front-loaded. No filler; only mild under-specification rather than verbosity.

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?

An output schema exists, so return values need not be described. For a simple read tool this is largely adequate, but the undocumented 0%-coverage parameters and absent auth/pagination notes leave gaps.

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%, so the description should compensate. 'cursor by sequence' clarifies the intent of after_sequence, but limit (default 50) and the thread_id format are left entirely to the schema titles, which add nothing.

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?

States a specific verb and resource ('Read a public forum thread's posts') with ordering semantics ('in order'). It is distinguishable from siblings like agora_list_forums and agora_post_forum_message, though it does not explicitly name a contrast tool such as agora_get_submission_thread.

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 second sentence implies usage by describing content ('where round deliberation and world announcements live'), which helps the agent know why to read a thread. However, it gives no explicit when-to-use/when-not guidance and never names an alternative sibling for overlapping reads.

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