load_arxiv_paper

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

No annotations are provided, so the description carries the full burden. It reveals the high-level behavior (downloading and building a graph) but does not disclose important behavioral traits like network requirements, caching semantics, whether existing graphs are overwritten, or the meaning of the refresh and main_file parameters. This leaves an agent guessing about side effects.

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 a single front-loaded sentence with no filler. Both the action and the expected outcome are present, and every word contributes to the purpose.

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 three parameters, no annotations, and no output schema, the description is too thin to be complete. It omits usage context, parameter semantics, side effects, and what the returned theorem graph looks like, leaving too much implicit for an agent to safely invoke the tool.

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 description coverage is 0%, so the description must compensate, but it does not explain any parameter. The word 'arXiv' hints that arxiv_id is the paper identifier, but there is no guidance on refresh semantics or main_file's role in choosing a file from the source project.

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 states a concrete action ('Download an arXiv source project') and a concrete result ('build its theorem graph'), so an agent can tell what the tool does. It does not explicitly contrast itself with the sibling load_paper, which appears to serve a similar loading purpose, so it misses full sibling differentiation.

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 described purpose implies when to use it: when an arXiv source project needs to be unpacked and its theorem graph constructed. However, it gives no explicit conditions, prerequisites, or exclusions, and it does not guide the agent on choosing between load_arxiv_paper and the sibling load_paper.

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