load-thread

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds that it loads metadata and comments and supports timestamp filtering/pagination, which is useful but does not disclose details like pagination mechanics or response shape beyond what annotations/schema already imply.

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 concise and front-loaded: it states the primary action and resource first, then mentions filtering/pagination in a compact second sentence. No redundant filler or repetition of schema details.

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 is adequate for a read-only operation with a rich schema and output schema. However, it doesn't clarify how pagination works (e.g., whether limit is the only control or if there is an offset/cursor), and it doesn't mention the distinction from load-conversation, which an agent might need to choose 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%, so all five parameters are documented in the schema. The description adds only a high-level hint about timestamp filtering and pagination, which maps to newerThanDate, olderThanDate, and limit. No additional parameter meaning beyond the schema is provided.

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 clear verb ('Load') and resource ('a thread'), and specifies that it returns metadata and comments. It does not explicitly distinguish itself from the sibling load-conversation, but the resource and filtering details make the core purpose clear.

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 usage: use this when you need a thread's metadata and comments, and mentions filtering by timestamp and pagination. However, it does not explicitly contrast with siblings like load-conversation or fetch-inbox, nor state when not to use this tool.

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