extract_concepts

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

With no annotations, the description carries the full burden. It implies a read/scan operation but never states that it is read-only, whether it recurses into subfolders, how it handles a null folder, or any cost/rate characteristics. For a filesystem-scanning tool this is a material 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?

One-line purpose statement front-loaded, followed by a compact Args block with no filler. The docstring-style formatting is slightly verbose relative to the schema but costs nothing in clarity.

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?

An output schema exists, so return values need not be explained. However, with no annotations and an optional, nullable folder parameter, the description should clarify default folder behavior and whether the scan is recursive—details an agent needs to call it correctly.

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%, but the description compensates by documenting both parameters: vault_path as the absolute path to the Obsidian vault and folder as the folder inside it to scan. It does not explain what a null/default folder means, which is the one remaining ambiguity.

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?

States a specific verb and resource: 'Extract recurring compiler concepts from notes in a vault folder.' An agent knows exactly what it produces and from where. It does not, however, distinguish itself from siblings like get_learning_gaps or compare_notes_to_project, so a 5 is not warranted.

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?

There is no guidance on when to use this tool versus the sibling tools, nor any stated preconditions (e.g. notes must exist, folder must be inside the vault). The scope 'recurring concepts' hints at intent but gives no exclusions or alternatives.

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