verify_quality

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

With no annotations, the description carries full burden for behavioral disclosure. It says 'scan' and 'return them for enrichment' which suggests read-only, but does not explicitly state that it does not modify data or confirm safety. It also does not disclose output format, permissions, or side effects. The description is too vague.

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 that efficiently conveys the core action and outcome. It is front-loaded and contains no filler. However, it could benefit from a bit more structure or clarity on return format, but it is not verbose.

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?

With 2 parameters, no output schema, and no annotations, the description should provide more context about what 'return them' means (list of entry IDs? entry objects? how to use with update_entry?). It also does not clarify whether project_dir is optional or defaults to current project, leaving ambiguity. Incomplete for a tool that feeds into a workflow.

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 100% with inline descriptions for both parameters. The tool description adds no additional meaning beyond what the schema already provides for project_dir and min_reason_chars. Baseline 3 is appropriate since schema already documents parameters well.

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 states the tool scans entries for specific quality issues (legacy schema, thin reasoning, missing tags, isolated entries) and returns them for enrichment via update_entry. The verb 'scan' and the listed issue types give a clear purpose, and it distinguishes from siblings like update_entry (modification) and query_entries (general query).

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?

The description implies a workflow (scan then enrich via update_entry) but offers no explicit guidance on when to use verify_quality versus alternatives like query_entries. It does not mention when-not to use or prerequisites. The mention of update_entry is a hint but insufficient.

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