label_paper

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

With no annotations, description should disclose side effects, permissions, and behavior of extra params like fit_score/fit_reason. Only mentions basic label actions, leaving agent uninformed about mutation behavior or return value.

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?

Single sentence is concise but too brief for a 6-parameter tool. Lacks structured breakdown of parameters or usage patterns.

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, description fails to explain interaction between set/add/remove, the role of fit_score/fit_reason, or any prerequisites. Incomplete for guiding correct invocation.

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 0%, so description must explain all params. Only 'labels' is implied, but 'add', 'remove', 'fit_score', and 'fit_reason' are not mentioned, leaving their purpose unclear.

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 the tool's action (set, add, remove) and resource (labels on a paper note). It distinguishes from siblings like add_paper or move_paper by focusing on label manipulation.

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?

No guidance on when to use this tool vs alternatives like mark_paper or list_papers_by_label. Missing instructions on when to use set vs add/remove or how labels interact with other features.

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