oncofiles

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the core action (exchanging code for tokens and storing them), which implies a write operation with authentication needs. However, it lacks details on error handling, token storage specifics, security implications, or rate limits. The description adds some value but is incomplete for a tool handling sensitive OAuth tokens.

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 front-loaded with the main purpose in the first sentence, followed by a clear parameter explanation. It uses minimal words without redundancy, and every sentence serves a functional role—no wasted text.

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's complexity (OAuth token exchange) and the presence of an output schema (which likely covers return values), the description is reasonably complete. It covers the purpose and parameter semantics adequately. However, for a security-sensitive tool, additional context on authentication flows or error cases could enhance completeness, though the output schema mitigates this gap.

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 description includes an 'Args' section that explains the 'code' parameter as 'The authorization code from the Google OAuth redirect,' adding semantic meaning beyond the input schema's basic type definition (string). Since schema description coverage is 0%, this compensates well for the single parameter, though it could specify format or validation details.

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 explicitly states the tool's purpose: 'Exchange an OAuth authorization code for tokens and store them.' This is a specific verb ('exchange') + resource ('OAuth authorization code') combination that clearly distinguishes it from sibling tools like 'gdrive_auth_status' or 'gdrive_auth_url', which handle different aspects of authentication.

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 usage context by mentioning 'authorization code from the Google OAuth redirect,' suggesting it should be used after receiving such a code. However, it does not explicitly state when to use this tool versus alternatives like 'gdrive_auth_url' (which might generate the code) or other auth-related tools, nor does it provide exclusions or prerequisites beyond the code requirement.

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