source_list_drive

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

No annotations are provided, so the description carries the burden. It discloses that freshness checks are performed by default and that skip_freshness speeds up listing, which are important behavioral details. It does not mention destructiveness or permissions, but for a listing tool, this is adequate.

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 extremely concise: two sentences for purpose and usage, then two bullet points for parameters. No extraneous words, well-structured, and front-loaded with the main action.

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 tool has an output schema (not shown), the description doesn't need to detail return values. It covers the main inputs, provides usage context relative to a sibling, and discloses a key option (skip_freshness). It is comprehensive for a listing tool with two 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 coverage is 0%, so description must compensate. It explains skip_freshness's effect ('skip per-source freshness checks for faster listing'), adding value beyond the schema. notebook_id is described as 'Notebook UUID', which is sufficient. Overall, it clarifies parameter behavior.

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 tool's function: 'List sources with types and Drive freshness status.' It also distinguishes itself by suggesting use before source_sync_drive, which differentiates it from sibling tools.

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 explicitly says 'Use before source_sync_drive to identify stale sources,' providing a clear usage context. However, it does not specify when not to use it or list alternative tools, but the context is sufficient for guidance.

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