batch_analyze_model_quality

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

With no annotations provided, the description carries the full burden. It discloses read-only opening (a safety signal) and continuation after errors, which are useful. However, it omits critical behaviors such as whether documents are saved, whether reports are generated (despite report_dir and report_name parameters), and what the return value or output format is. The mention of read-only adds value but is insufficient.

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, efficient sentence that front-loads the core actions (open read-only, run checks, close, continue on errors). It contains no filler and is appropriately concise for the information it conveys.

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?

For a tool with 13 parameters, no output schema, and no annotations, the description is grossly incomplete. It does not explain what the tool returns, how to configure the analysis scope, what report formats are supported, or how errors are surfaced. An agent cannot invoke this tool correctly based on the description alone.

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 does not explain any of the 13 parameters. It mentions 'naming/spec quality checks' which likely maps to the 'analyses' parameter, but provides no details on root, limit, paths, recursive, extensions, report_dir, rules_path, report_formats, or continue_on_error. The description fails to compensate for the lack of schema documentation, leaving agents without essential parameter understanding.

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 action (open models read-only), the resource (models), and the purpose (naming/spec quality checks). It also mentions the batch nature and error continuation. However, it does not explicitly contrast with sibling tools like analyze_naming_issues or analyze_spec_issues, which could be confused for single-document versions.

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 provides no guidance on when to use this batch tool versus the single-document analyzers or other related tools. It implies a batch scenario but does not state selection criteria, exclusions, or alternatives. An agent cannot determine when this is the preferred tool.

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