oahelper_sync

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

With no annotations the description carries the full burden, and it does well: it discloses ordering ('newest sets first'), a per-call request budget tied to max_items, cost semantics ('already-saved items cost nothing'), and quota rationale for the exclusion. It stops short of stating auth requirements or failure behavior, so 4 rather than 5.

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?

Front-loaded with the action, then budget behavior, then the sibling alternative, then where to read output. Each sentence adds information, though the multi-line layout is slightly denser than needed.

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?

Output schema exists, so return format needn't be explained, and the description usefully points to library/<company>/index.md. However, for a 4-param tool with 0% schema coverage, leaving include_images and include_interviews unexplained is a real gap in an otherwise thorough definition.

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% and there are 4 params, so the description must compensate. It only explains max_items (live requests per call); include_images and include_interviews are never mentioned, and the 'cost nothing' note only loosely implies idempotent behavior. Two of four parameters remain fully 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?

States a specific verb ('Download') plus a specific resource ('one company's OAHelper content into the offline library') and enumerates the content types (set lists, question statements, MCQ answers, interview experiences). It also carves out what it does NOT do, routing the agent to the oahelper_solution sibling.

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?

Explicitly states the repeat-call pattern ('call it again to continue') and explains the exclusion condition for official solutions ('NOT fetched here because each one uses the account's daily solution quota; use oahelper_solution'). Both when-to-use and when-not-to-use are covered.

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