nexo_transcript_read

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

With no annotations, the description carries full burden. It indicates a read operation but fails to explain the 'fallback' behavior, any prerequisites, or side effects. Minimal behavioral context.

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?

Single sentence is concise, but front-loading is acceptable. However, it lacks structure to convey key information like parameter purposes or usage context.

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?

Lacks details on return format, which is critical since there is no output schema. The description does not fully address what a 'full transcript fallback' entails or how to use the parameters effectively, leaving significant gaps.

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?

0% schema description coverage requires the description to explain parameters, but it only lists possible identifiers (session id, display name, etc.) without mapping them to the actual parameters (client, session_ref, max_messages, transcript_path). max_messages is not mentioned at all.

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 it reads a full transcript fallback by various identifiers, clearly indicating the verb and resource. However, it does not differentiate from sibling tools like nexo_transcript_recent or nexo_transcript_search, and 'fallback' is ambiguous.

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 explicit guidance on when to use this tool versus alternatives. The term 'fallback' suggests a secondary option but without clarification. No exclusions or when-not-to-use context.

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