Extract paper facts

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

With no annotations provided, the description carries the full burden. It does disclose useful behavioral traits: the extraction is deterministic, facts have source locators, and unsupported values are not inferred. However, it does not explain side effects, prerequisites, URL handling, or failure behavior, which leaves some important transparency gaps.

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 with no wasted words. It front-loads the core action and constraint, and the second clause adds important behavioral nuance without bloating the text.

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 the simple one-parameter schema, the description is not complete enough given the crowded sibling toolset. It does not explain what counts as a 'fact', what the output looks like beyond source locators, or how this differs from extract_paper_claims. With no output schema and no annotations, the description needs to carry more weight.

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%, and the description never mentions the `url` parameter. The parameter's purpose can only be inferred from the property name and the tool name, not from the description itself. The description should clarify that the URL points to the paper to analyze, but it does not.

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 names a specific operation ('Extract deterministic heuristic facts') and adds a defining constraint ('with source locators; no unsupported values are inferred'). This is clearer than a tautology, but it does not explicitly differentiate from the many sibling extraction tools like extract_paper_claims or extract_training_parameters.

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 usage guidance is provided. The description does not say when to prefer this tool over extract_paper_claims, verify_claim, or other extraction-focused siblings, nor does it state conditions or exclusions. The only hint is the phrase 'deterministic heuristic facts', which is too weak to route an agent confidently.

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