get_thread

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

No annotations provided. Description states 'Read' implying read-only, but fails to disclose pagination behavior, error handling, authentication needs, or rate limits. The 'page' and 'limit' parameters suggest pagination but are not explained.

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 concise sentences with a clear action and example. No wasted words, front-loaded with the purpose.

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?

Adequately explains what the tool does and how to provide the thread URL. However, missing details on pagination defaults, response format, and error scenarios. Without output schema, more behavioral context would help.

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 67%. Description repeats thread_url concept but does not elaborate on 'page' or 'limit' parameters. No added context for their usage beyond what schema provides.

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 'Read posts from a HotCopper thread', specifies the verb and resource. Provides URL examples, distinguishing from siblings like 'latest_posts' or 'stock_threads' by focusing on a single 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?

Implies usage for retrieving a specific thread's posts but lacks explicit when-to-use vs alternatives like 'latest_posts' or 'search'. The description gives input format guidance but no exclusions.

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