list_threads

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

Annotations already declare readOnlyHint=true, so the description's 'browse' aligns with that. The description adds no additional behavioral details beyond the annotation, such as pagination, result limits, or ordering. It is adequate but does not enrich the safety profile.

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 extremely concise: one sentence plus a parenthetical note. Every word adds value, and the key verb 'browse' is front-loaded. There is no redundancy or wasted text.

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?

The description tells the agent how to obtain the nodeId and what the tool does, but it does not describe the output format, pagination, or what fields each thread will contain. With no output schema, this lack of information reduces completeness. It is adequate for a simple list operation but leaves 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?

The input schema has 50% description coverage (nodeId has a description, page does not). The tool description does not mention parameters at all, so it fails to compensate for the missing page parameter description. The nodeId description in the schema is good, but the overall parameter context is lacking.

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 tool browses threads in a forum section using the verb 'browse' and resource 'threads'. It distinguishes itself from sibling tool list_forums by noting that list_forums should be used to obtain nodeIds. This is specific and unambiguous.

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 explicitly instructs the agent to use list_forums to get valid nodeIds, providing a clear prerequisite. It implies the tool is for browsing all threads in a section, contrasting with search_forum and get_thread siblings. However, it does not explicitly state when not to use it.

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