extract_methodology

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The one-line description does not state whether this is a read-only operation, whether the paper must already be retrieved/known to the system, whether it returns a structured or narrative result, or any limitations of the extraction. For a tool with zero annotation coverage, this is a meaningful gap.

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?

A single sentence with no filler; every word contributes to the stated purpose. It is appropriately front-loaded and free of redundancy.

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 and only two parameters, the description is under-specified. It omits the wider context an agent needs: whether this operates on papers already in the system, how it relates to sibling extraction tools like extract_limitations, and what distinguishes its behavior from summarize_paper. A slightly richer description would materially improve call success.

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 adds no parameter detail — title and abstract are documented only as bare strings. The phrase 'from a paper' loosely suggests these identify the source paper, but the description does not explain their format, relationship, or required content. The description fails to compensate for the missing schema documentation.

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 ('Extract') and resource ('methodology and technical approach from a paper'), making the tool's job clear. However, it does not distinguish itself from the sibling extract_limitations, which shares the same extraction pattern — an agent must infer the difference from the resource type alone.

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 is given on when to use this tool versus alternatives. It neither mentions extract_limitations, summarize_paper, or find_research_gaps, nor states any conditions or exclusions. Usage timing is only implied by the verb-noun phrasing, leaving the agent to guess.

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