literature

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

With no annotations, the description must carry the full behavioral burden. It does disclose the data source (SIMBAD bibliography), recency ('Recent papers'), and a mode constraint ('Open mode only'), but it leaves the recency window undefined, does not describe return shape or ordering, and never explains what open mode actually restricts.

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 three sentences are front-loaded with the tool's purpose and contain little waste. The independence caveat is relevant, though its phrasing ('if you want your investigation to count as independent') is slightly editorial and could be tighter.

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?

For a simple one-parameter retrieval tool with no output schema, the description covers purpose, source, mode, and usage timing. However, it leaves the required 'case' parameter undefined and the 'Open mode only' constraint unexplained, which are meaningful gaps for 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 description coverage is 0% for the single required parameter 'case', and the description does not compensate. It refers only to 'the target' and never clarifies whether 'case' is a case identifier, a target name, or what format is expected, leaving the parameter substantially unexplained.

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 retrieval action and source: recent papers mentioning the target from the SIMBAD bibliography. It is clear what the tool returns in kind, though it does not distinguish itself from likely siblings such as prior_art or explain how its bibliography scope differs.

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?

It gives explicit timing guidance: read the papers after forming your own view, not before, to preserve an independent investigation. It also states 'Open mode only,' which implies a usage constraint, but it never explains what open mode means or which alternative to use when that constraint is not met.

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