workspace_add_arxiv_paper

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

'Add or replace' does disclose that this operation can mutate and potentially replace an existing project, which is valuable given no annotations. But it does not explain what replacement destroys, whether an active workspace is required, what happens if the project already exists, or any side effects. With no annotations, the description carries the full safety burden and misses critical details.

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 or redundancy. It clearly communicates the core operation and object in a compact way, which is appropriate for this dimension.

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?

This is a mutating tool with no annotations and no output schema, yet the description omits prerequisites, the meaning of refresh, the role of main_file, and the consequences of replacement. The one-sentence description is insufficient for an agent to safely and correctly invoke this tool in varied situations.

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?

The description provides no per-parameter detail for arxiv_id, refresh, or main_file, and schema description coverage is 0%. The words 'arXiv' and 'LaTeX project' add domain context, but the agent still has to guess how refresh behaves and what main_file means. This does not adequately compensate for the absent schema 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?

The description states a specific verb ('Add or replace'), a concrete resource ('arXiv LaTeX project'), and a clear location ('active workspace'). It distinguishes itself from siblings like workspace_add_local_paper and load_arxiv_paper by specifying the arXiv/LaTeX domain and the workspace target.

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 phrase 'in the active workspace' implies this tool should be used when the agent intends to add or replace an arXiv project in the currently open workspace. However, it does not explicitly state prerequisites, when to choose this over load_arxiv_paper or workspace_add_local_paper, or when replacement is appropriate.

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