tapatalk_get_thread_by_unread

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

The annotation readOnlyHint=true already signals a safe read operation. The description adds valuable context about authentication dependency and its impact on unread tracking accuracy, which is not conveyed by annotations. It does not detail edge cases like no unread posts, but the burden is partially covered by the readOnlyHint.

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 highly concise: two short sentences, front-loaded with the core action, and no redundant information. Every word earns its place.

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 tool with one parameter, a readOnlyHint, and no output schema, the description covers the essential functionality and the auth caveat. It lacks explicit mention of return format or behavior when there are no unread posts, but the tool's purpose is conveyed clearly enough for an agent to use it correctly.

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%: topic_id is described as 'Topic ID to read'. The tool description does not add any additional parameter semantics beyond what the schema already provides, so the baseline score of 3 applies.

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 action ('Jump to the first unread post in a topic') with a specific verb and resource. It distinguishes from siblings like tapatalk_get_thread (normal thread fetch) and tapatalk_get_unread_topics (list of unread topics) by focusing on the first unread post navigation.

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 provides clear context: it is for jumping to the first unread post, and mentions that authentication is required for accurate tracking. However, it does not explicitly state when to use this tool over alternatives or mention exclusions, so it stops short of a 5.

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