source_sync_drive

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only mentions 'refresh' and the source_id parameter effect, but does not reveal what 'refresh' entails—whether it overwrites data, requires permissions, or has side effects. This is insufficient for a mutation-type operation.

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 sentence, front-loaded with the action and resource, and contains no filler. Every word is functional, making it appropriately concise.

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?

Despite having an output schema, the description is too terse for a tool that performs a mutation. It does not explain what 'refresh' means, what prerequisites exist (e.g., authentication or existing Drive link), or what the output represents. The required notebook_id parameter is not documented, leaving the tool incomplete for straightforward use.

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 must compensate. It does add meaning for source_id ('If source_id is None, refresh all'), but it fails to explain notebook_id, a required parameter. With two parameters, half are undocumented, leaving a significant gap in parameter understanding.

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 purpose: 'Refresh Drive-linked sources.' It specifies the action (refresh), the resource (Drive-linked sources), and includes a scope condition ('If source_id is None, refresh all') which adds specificity and distinguishes it from sibling tools like source_add or source_get_content.

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 implies when to use the tool (when you want to refresh Drive-linked sources) and even clarifies behavior for a specific parameter, but it does not provide explicit alternatives or when-not-to-use guidance. Sibling tools like source_get_content or source_add are not referenced, so the usage context is only implied.

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