load-conversation

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful behavior context by noting that metadata and messages are returned and that timestamp filtering/pagination are supported, but it does not explain ordering semantics, behavior when both date filters are provided, or pagination mechanics beyond the schema's limit field.

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 short sentences cover the core purpose and key capabilities without wasted words. The main operation is front-loaded and the supporting capabilities follow concisely.

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 read-only fetch tool with a full input schema and an output schema, the description provides enough scope: it names the resource type, the returned components, and the available filtering/pagination options. Minor behavioral details like result ordering are not specified, but the annotations and schema fill most 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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds a high-level grouping of timestamp filtering and pagination but does not provide additional meaning beyond the schema definitions.

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?

Description uses a specific verb ('Load') with a clear resource ('a conversation (direct message)') and scope ('with its metadata and messages'). It also mentions filtering and pagination, which clearly separates it from thread-loading or search tools.

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 establishes clear context: this tool loads direct-message conversations, not threads, and supports timestamp filtering and pagination. It does not explicitly name alternatives or state when not to use it, but the 'direct message' qualifier gives enough context to route an agent correctly among the sibling tools.

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