list_orphan_papers

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

No annotations are provided. The description only mentions it is an alias, lacking behavioral details such as side effects, permissions, or output nature. It does not describe the action's effect beyond listing orphans.

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 sentence, very concise. However, it omits parameter details and could provide more context about the tool's use. It is lean but incomplete.

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?

Despite having an output schema, the description does not explain the return values or behavior. Parameter documentation is missing, and the overall context for using the tool is insufficient.

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% with one parameter 'folder' having no description. The description adds no information about this parameter, leaving the agent without guidance on its purpose or format.

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 it is a deprecated alias for cluster_rebind with a specific action, clearly indicating the tool lists orphan papers. It distinguishes from siblings like add_paper or cluster_rebind itself.

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?

Explicitly states 'Deprecated alias' and names the alternative: cluster_rebind(action='list_orphans'). This tells the agent when not to use it and what to use instead.

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