openalex_get_fulltext_sections

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

Discloses that tool 'will trigger download if not cached', a key behavioral trait beyond what annotations provide (none given). No annotation contradiction. Could add more about side effects like network latency.

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?

Two sentences, front-loaded with the main purpose, no superfluous words. Efficient and clear.

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?

Covers purpose and side effect but omits return format, handling of missing sections, and caching details. With no output schema, more detail on output would improve completeness.

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 covers 100% of parameters with descriptions. Description adds default behavior for sections (all available) and expands on accepted identifiers (OpenAlex ID, DOI, PMID), providing value beyond the schema.

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?

Description clearly states 'Get extracted sections from a downloaded paper' with a specific verb and resource. It also notes a side effect (trigger download if not cached), distinguishing it from sibling tools like openalex_download_fulltext and openalex_get_work.

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 guidance on when to use this tool versus siblings, nor any when-not-to-use conditions. The description does not mention prerequisites or context for triggering downloads.

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