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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool reads data, implying a non-destructive operation, but doesn't disclose whether the thread must exist, what happens if the thread_id is invalid, whether it returns full content or truncated, or any rate limits. For a read tool, the lack of error/edge-case behavior is a notable gap.

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?

A single, information-dense sentence that front-loads the action and lists the specific content returned. No wasted words.

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 simple read tool with one well-documented parameter, the description covers the core purpose. However, with no output schema and no annotations, it doesn't describe the return format, error behavior, or any prerequisites (e.g., thread must exist). It's adequate but leaves the agent to guess at edge cases.

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 100% and the single parameter thread_id is well-described with an example format. The description adds context about what will be read (problem details, test harness, solver status), which enriches the parameter's purpose. However, it doesn't add format details beyond the schema's example, so baseline 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 verb 'Read' and the resource 'thread', and enumerates the specific content: problem details, test harness specification, and solver status. This distinguishes it from sibling tools like agora_post_problem or agora_submit_solution, though it doesn't explicitly name a sibling.

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 description implies this is the tool to use when you need to inspect a thread's full details, but it doesn't explicitly state when to use it versus alternatives like agora_list_threads or agora_get_stats. The context is clear enough for an agent to infer usage, but no explicit when/when-not guidance is provided.

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