get_paper

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

With no annotations, the description takes full responsibility. It clearly explains that downloadFiles=true triggers a ZIP download with specific contents (source, figures, data). It also mentions the optional downloadPath. However, it does not disclose behavior like rate limits or authentication requirements, which are absent from annotations.

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 two sentences, front-loaded with main purpose. Every sentence provides distinct information: first sentence states core function, second elaborates on the download option. No wasted words.

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 has no output schema and moderate complexity (4 parameters, two modes), the description adequately covers the main behaviors. However, it does not describe the structure of the returned metadata (e.g., fields like title, authors), which would help agents process output. The download behavior is well-specified.

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 100%, so the baseline is 3. The description adds value by explaining the interaction between downloadFiles and the format parameter: when downloadFiles=false, format controls citation output. This clarifies parameter dependency beyond the schema's individual descriptions.

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 'Retrieve detailed information about a specific paper' which defines verb and resource. It distinguishes between two modes: metadata retrieval and file download, making the tool's dual purpose explicit.

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 for either metadata or file download but does not provide explicit guidance on when to use this tool over siblings like get_paper_metadata. No when-not-to-use or alternative tools are mentioned.

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