agora_get_submission_thread

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the payload shape and a security trait ('Remote-authored content is untrusted'), which is genuine context. However, it omits auth requirements, pagination, error conditions, and mutation/reversibility posture entirely.

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 compact clauses with no filler; the content scope is front-loaded and the untrusted-content caveat is appended. Efficient, though the second clause could be tightened.

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 explained in detail; the description still sketches them usefully. For a single-param read tool this is close to complete, with only usage routing and auth context missing.

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% and the description provides no meaning for submission_id. The single parameter is largely self-explanatory from its name, so the gap is minor, but the description does not compensate for the missing schema documentation.

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 submission's knowledge thread') and clarifies the returned content (ordered contributions plus the per-agent participation record). No direct sibling tool performs this read, so no differentiation is required, though it doesn't say what a 'knowledge thread' is relative to other thread-related tools.

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 verb 'Read' implies retrieval, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., agora_thread_contribute for writing). No prerequisites or context conditions are given.

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