Return the ENTIRE corpus including premium resource bodies in one document — the keyed deliverable of the Corpus/Enterprise license. Requires a Corpus- or Enterprise-tier api_key (a Starter key unlocks premium resources but NOT the corpus file); without an entitled key a payment-required/upgrade object is returned. The free, premium-stubbed version is get_corpus.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Corpus/Enterprise license key (cg_...) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that an unauthorized key returns a payment-required/upgrade object, and that it returns entire corpus in one document. No annotations to contradict; fully self-contained.
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 sentences each carrying distinct information: purpose, licensing requirement, and alternative. No redundancy.
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?
With only one parameter and no output schema, the description sufficiently covers what the tool returns, when to use, and error behavior. No gaps.
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 already describes api_key; description adds the specific format and license requirement, going beyond schema alone.
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?
Clearly states verb 'Return' and resource 'corpus' with scope 'ENTIRE including premium resource bodies'. Distinguishes from sibling 'get_corpus'.
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 required license level (Corpus/Enterprise), what Starter key does vs not, and the alternative 'get_corpus' for free version.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action: checking access, fetching corpus (free vs full), pricing, payment, listing, searching, stats, and single resource retrieval. No significant overlap.
All tools follow a consistent verb_noun pattern in snake_case (e.g., check_access, get_corpus, list_resources). Verbs are uniform and descriptive.
With 10 tools, the set is well-scoped for a resource access and management API. Each tool serves a clear purpose without redundancy or excessive number.
The toolset covers core operations: access verification, corpus retrieval (free and premium), pricing, payment info, resource listing, search, and stats. Missing write operations (e.g., purchase), but acceptable for a read-focused server.