nexo_transcript_read

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

With no annotations, the description must disclose behavioral traits. It only states 'Read' (implying non-destructive) but does not confirm read-only behavior, output expectations, or any side effects. No warnings or constraints are provided.

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 concise sentence with no redundant information. However, it could be more structured by clearly mapping identifiers to parameters.

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 lack of output schema and annotations, the description should cover expected return values, pagination (max_messages usage), and edge cases. It does not address these, leaving significant gaps for a tool with four parameters.

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 the description should compensate. It lists 'session id, transcript display name, session_uid, or exact path' but these do not directly map to schema parameters (session_ref, transcript_path, client, max_messages). The parameter 'client' and 'max_messages' are not mentioned, causing ambiguity.

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 action 'Read' and the resource 'full transcript fallback', listing multiple identification methods (session id, display name, session_uid, path). This distinguishes it from sibling tools like nexo_transcript_recent and nexo_transcript_search, though the term 'transcript fallback' is not fully explained.

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 is provided on when to use this tool versus its siblings (e.g., nexo_transcript_search, nexo_transcript_recent). The description does not mention prerequisites or exclusions, leaving the agent to infer usage context.

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