read_chatgpt_conversation

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool 'never types, submits, or uploads anything,' establishing a read-only safety profile, but says nothing about authentication needs, rate limits, timeout behavior, or what happens when the conversation is missing.

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?

Three tight sentences with the core purpose front-loaded and the safety constraint and URL prerequisite following in priority order. No filler.

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?

No output schema exists, so the description reasonably explains the return (latest assistant response), but it leaves three of four parameters unexplained and omits failure/timeout behavior. For a 4-param tool with zero annotation and zero schema-description coverage, more is needed.

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% across 4 parameters, and the description only clarifies the required conversation_url (canonical chatgpt.com/c/... format). timeout_seconds, expected_message_id, and minimum_response_characters are left entirely undocumented in both schema and description.

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 — reading the latest assistant response from an existing ChatGPT conversation — and scopes it narrowly ('latest assistant response'), which distinguishes it from ask_chatgpt's create-and-send behavior. An agent can tell what it retrieves without opening the schema.

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?

Explicitly frames the tool as 'recovery-only' and requires the canonical URL returned by a previous ask_chatgpt call, giving both the situation (recovery) and the dependency. It stops short of naming an alternative tool or an explicit when-not-to-use condition.

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