nexo_transcript_recent

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

No annotations provided, so the description carries full burden. It does not disclose what 'visible to NEXO' means, how results are ordered, pagination behavior, or what happens if no transcripts are found. The description lacks behavioral depth.

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?

Extremely concise (one sentence), which is efficient but sacrifices necessary detail. Front-loads purpose but omits usage and parameter info. Conciseness is not valuable at the expense of completeness.

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?

With 3 parameters, no annotations, and no output schema, the description is insufficient for effective use. An agent lacks information to set parameters correctly or interpret results. The tool's complexity is not served by this minimal description.

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 coverage is 0%, yet the description does not explain the three parameters (hours, client, limit). The agent gets no clue about their meaning, constraints, or defaults. This is a critical gap.

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?

Clearly states it lists recent transcripts visible to NEXO. The verb "list" and resource "transcripts" are specific, and the qualifier "recent" gives temporal context. However, it doesn't differentiate from nexo_transcript_read or nexo_transcript_search, which list or search transcripts respectively.

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 other transcript tools. No mention of use cases, prerequisites, or exclusions. The description is purely functional without context for selection.

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