download_repec

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

The description fully discloses that the parameters are unused and that the tool returns an error message with alternatives. Since no annotations are provided, the description carries the entire burden and does so transparently.

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 well-structured with a clear note, an ordered list of alternatives, an args section, and a returns section. Every sentence adds value without 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?

Given that this tool does not perform a real download, the description completely covers its behavior, limitations, and alternatives. No output schema exists, but the return value is described sufficiently.

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?

Despite 0% schema description coverage, the description adds crucial meaning: both parameters are explicitly stated as unused. This is vital for the agent to understand that the tool ignores its inputs.

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?

The description clearly states that the tool does not directly download PDFs because RePEc is a metadata index. It explicitly mentions the verb 'download' and the resource 'RePEc', and distinguishes itself from siblings like download_arxiv by explaining the limitation.

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 provides explicit alternatives ordered by priority: first visiting the paper URL, then using download_scihub. It tells the agent exactly when to use this tool (to get alternatives) and when to use others, which is perfect guidance.

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