get_conversation_history

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It mentions 'paginated' and 'targeted data,' but it does not reveal key behaviors like the default messageTypes filter (['user']) to reduce data volume, or whether the operation is read-only. It also fails to mention pagination limits or response format, which are important for an API with no output schema.

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 a single, front-loaded sentence that immediately states the action and then provides usage context in parentheses. Every word earns its place, with no redundant or filler content.

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?

Given the tool has 7 parameters, no output schema, and no annotations, the description should provide more context about expected return values and important behaviors. It omits any mention of response structure, default message filtering, or how to use parameters together. The description is too brief to be considered complete for a tool of this complexity.

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 baseline is 3. The description adds minimal parameter meaning beyond the schema, only hinting at 'targeted data' which suggests filtering capabilities. It does not elaborate on how parameters interact (e.g., startDate/endDate requiring timezone), but the schema definitions already provide clear descriptions.

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's purpose with a specific verb and resource: 'Get paginated conversation history.' It also distinguishes itself from sibling tools by positioning it as a follow-up to list_projects/list_sessions for targeted data retrieval, making it unique.

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 guides when to use this tool: 'use after exploring with list_projects/list_sessions for targeted data.' This provides clear context and implies that list_projects/list_sessions are for broader exploration. However, it does not explicitly mention when not to use it or compare with search_conversations, so it lacks full exclusion guidance.

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