set_extraction

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

With no annotations provided, the description must bear the full burden of behavioral disclosure. It only states the two actions but does not explain side effects, reversibility, requirements, or what happens when parameters are null. This is insufficient for a configuration mutation tool.

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 concise sentence that front-loads the main actions. It avoids unnecessary words, though the phrase 'and/or' is slightly awkward. It earns its place but is terse.

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?

Given the lack of annotations and output schema, the description should explain what the tool does beyond the bare action. It does not mention return values, behavior of null inputs, or any downstream effects. For a simple tool this is minimal but still leaves the agent with limited context 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%, so the description must compensate. It hints at parameter roles by mentioning 'Toggle' (implying 'enabled') and 'set a custom extract path' (implying 'custom_path'), but it does not describe the parameters explicitly or explain their interaction or defaults beyond what the schema already titles.

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 identifies the tool's dual function: toggling the extraction extension and setting a custom extract path. It uses specific verbs ('Toggle', 'set') and a specific resource ('extraction extension', 'custom extract path'), distinguishing it from generic sibling tools like set_enabled and set_download_dir.

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 provided on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or contrast with sibling tools such as set_enabled for toggling or set_download_dir for path settings. The usage context is entirely absent.

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