get_conversation_details

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

Annotations already declare readOnlyHint=true, so the description correctly implies read-only. However, it adds no extra behavioral traits like pagination, error handling, or performance considerations. The description does not contradict annotations.

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?

Very short (3 lines), front-loaded with purpose. Each sentence is useful. The 'Args:' line is a minor redundancy but acceptable. No wasted words.

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?

Output schema exists, so return values need not be described. The description covers the main purpose and key parameters. However, it does not mention sorting, pagination of messages, or scope (e.g., only user's own conversations). Adequate for a simple get operation.

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 0%, so description must compensate. It adds brief but meaningful descriptions for each parameter: 'Conversation ID', 'Mark as read when viewed', 'Include all messages'. This clarifies boolean defaults and intent, though could be richer.

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 'Get detailed conversation information with messages', a specific verb+resource combination. It distinguishes from siblings like 'list_conversations' (list only) and 'get_discussion_topic_details' (discussion topics vs conversations).

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?

No guidance on when to use this tool versus alternatives. No indication of prerequisites, context, or when NOT to use it. The parameters have defaults but no explanation of when to override them.

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