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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully reveals ordering ('newest activity first') and pagination ('50 per page'), which are not obvious from the tool name or schema. It does not mention auth or default page behavior, but the read-only nature of 'List' is strongly implied.

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?

The description is two short clauses with zero filler. The core action, scope, ordering, and page size are all front-loaded in a compact and readable way.

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 two-parameter paginated list tool, the description provides enough to make a correct call: board is required, page is optional, and results are ordered by recency. Without an output schema, it could say a bit more about what thread fields are returned, but this is not essential for invocation.

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?

The schema documents 'board' with an example but leaves 'page' largely undocumented. The description's '50 per page' clarifies that page is a pagination parameter, but the description does not explicitly map page numbers to the parameter or explain default behavior. It partially compensates for the 50% schema coverage gap.

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 states a specific verb ('List'), a specific resource ('threads'), and a clear scope ('on a board'). It is easily distinguished from siblings like list_boards and read_thread, so an agent can tell which tool to pick.

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 intended use is implied by the phrase 'on a board,' but the description does not explicitly say when to prefer this tool over list_boards or read_thread. There is no exclusion guidance or alternative routing.

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