check_local_transcripts

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool checks for locally available transcripts, implying a read-only operation, but doesn't specify whether it requires file system access, what happens if no transcripts exist, or the format of the return value (e.g., list of files, metadata). For a tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action ('check') and resource ('transcripts'), making it easy to parse. Every part of the sentence earns its place by conveying essential information.

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 complexity (1 parameter with nested objects, no output schema, and no annotations), the description is incomplete. It doesn't address parameter usage, return values, or behavioral details like error handling. For a tool that interacts with local files and has date-based filtering, more context is needed to guide effective use by an agent.

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 input schema has 1 parameter ('dateRange') with 0% description coverage in the schema (no descriptions for 'from' or 'to' in the nested object). The description doesn't mention any parameters, failing to compensate for the low schema coverage. It doesn't explain what 'dateRange' does (e.g., filters transcripts by date) or provide context for its use, leaving parameters undocumented.

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 verb ('check') and resource ('transcripts that are already downloaded and available locally'), making the purpose understandable. It distinguishes from siblings like 'download_transcript' (which downloads) and 'get_recent_transcripts' (which might fetch from a remote source). However, it doesn't explicitly contrast with 'list_meetings' or 'search_transcripts', leaving some sibling differentiation incomplete.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing downloaded transcripts first), exclusions, or comparisons to siblings like 'get_recent_transcripts' (which might retrieve from a server) or 'search_transcripts' (which might search content). This lack of context leaves the agent to infer usage scenarios.

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