oahelper_offline

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

With no annotations, the description carries the full behavioral burden, and it does disclose two real traits: the operation is a local/no-network read, and its output shape switches based on whether company is supplied. It does not mention staleness of the offline cache, sync prerequisites, or error behavior when a company is absent locally.

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?

Three short sentences, zero filler, with the core 'what is saved offline / no network call' framing front-loaded before the conditional behavior. Every sentence adds 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?

An output schema exists, so return-value detail is not the description's job, and for a single-optional-parameter read tool this covers the essentials. Missing only offline-cache freshness/sync prerequisites, which would help an agent avoid stale results.

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% and the sole parameter has no description, so the description must compensate — and it does, fully defining the parameter's two modes (omitted = list all companies, supplied = that company's index). It only lacks format examples (e.g., exact company identifier form).

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 resource (the offline-saved library) and a specific dual behavior: full company list without a company, and that company's index (sets, interviews, counts) with one. It implicitly separates itself from network-based siblings via 'No network call', though it never names oahelper_sync or oahelper_company by name.

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?

'No network call' implies the offline use case, which is genuine context for choosing this over a network-backed sibling. However, it never states when to prefer this over oahelper_company, oahelper_search, or oahelper_sync, so the selection logic is left for the agent to infer.

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