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

readOnlyHint=true already declares the safety profile, so the description's added value is the ordering guarantee and the 1000-item ceiling, which tells the agent results may be truncated. That is genuine behavioral context beyond the annotations, though it stops short of saying how truncation is signalled or paged.

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?

One front-loaded sentence carrying the resource, item types, ordering and cap, followed by a short endpoint reference. The REST endpoint line adds little for an agent choosing a tool, but nothing is padded or redundant.

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?

There is no output schema, so the description carries the return-shape burden; it does name the item types and ordering, which helps. However, the explicit 1000-item cap implies truncation without explaining whether or how an agent retrieves the remainder, which is a meaningful gap for a listing tool.

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 both conversation_id and session_id are already documented in the schema. The description adds no meaning beyond that — notably it never mentions the session_id filter or what a 'session' means in this timeline, so baseline 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?

States a specific verb and resource ('List the timeline items of a conversation') and enumerates the item types returned (messages, emails, calls, notes), which distinguishes it from gladly_get_conversation_item and gladly_get_conversation without needing the schema. It does not explicitly name those siblings as alternatives, so it falls just short of a 5.

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 ordering ('oldest first') and cap ('at most 1000') imply this is the bulk-read path for a conversation's history, but there is no explicit when-to-use guidance and no exclusion pointing to gladly_get_conversation_item for single-item fetches or gladly_get_conversation for metadata. Usage must be inferred from the sibling list.

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