Read a sci-bot conversation

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

With no annotations, the description carries the disclosure burden. It does indicate a read operation ('Returns'), a full-transcript behavior, and account scoping ('signed-in account'), which is useful. However, it does not disclose behavior on invalid ids, error responses, or whether authentication is explicitly required beyond the 'signed-in' phrase.

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?

A single sentence that starts with the verb, names the resource, and specifies scope. Every word earned its place; there is no fluff or redundancy.

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 one-parameter read operation with no output schema and no annotations, the description is mostly adequate: it says what is returned and to whom it is scoped. But it omits edge-case behavior (e.g., nonexistent conversation id) and does not reference scibot_conversations as the source of valid ids, a gap that the schema partially fills but the description does not.

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?

The schema provides 100% coverage for the single parameter with the description 'Conversation id from scibot_conversations', so the baseline is 3. The tool description does not add syntax or format details beyond what the schema already states.

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 states a specific action ('Returns'), a clear resource ('the full transcript of one conversation'), and a scope ('of the signed-in account'). It distinguishes itself from siblings like scibot_conversations (which likely lists conversations) by emphasizing a single conversation's full transcript.

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?

Usage is implied: use this tool when you need the full transcript of a specific conversation. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as scibot_conversations for listing conversations, which would help disambiguate in a large sibling set.

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