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

With no annotations, the description carries the full burden and does well: it discloses the resolution mechanisms (DOCTYPE ENTITY declaration for ICN, ids in the same document for internalRef), the enumerated failure reasons returned for unresolved references, and the special case that dmRefs to modelIdentCode S1000D point at the spec and are listed separately. It omits error behavior and cost/performance for large documents.

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 core purpose is front-loaded in the first clause, and the remaining clauses earn their space by enumerating kinds and failure reasons. It is dense to the point of being a run-on sentence with heavy parenthetical nesting, which costs readability but not correctness.

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 6-parameter, no-output-schema tool, the description covers what is checked, how each kind resolves, and what unresolved entries report (reason codes), which is the essential return information. It does not describe the overall result shape or the identity/count fields, leaving some return structure to be discovered at runtime.

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 coverage is 100%, so every parameter is already documented in the schema and baseline 3 applies. The description adds domain meaning by spelling out the reference kinds that the `kinds` enum selects and the ENTITY-declaration lookup path, but says nothing extra about csdbDirs, maxItems, or includeResolved.

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: list the references of one document plus whether each target exists. It then enumerates exactly which reference kinds are covered (dmRef, pmRef, ICN, internalRef, applicRefId), so an agent can tell this is a reference-resolution tool rather than a schema validator like validate_schema or verify_csdb.

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?

Usage is implied by the phrasing — one document, references, resolution status — but there is no explicit when-to-use/when-not framing and no mention of alternatives such as verify_data_module for structural checks or verify_csdb for CSDB-wide integrity. An agent must infer the boundary from sibling names.

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

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool reads under S1000D_SPEC_DIR, inspects brex.xsd for the issue, and reports available schema names, but it does not explicitly state that the operation is read-only, how failures are reported, or what the output structure looks like.

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?

Two sentences, front-loaded with the purpose and followed by the diagnostic use case. The parenthetical detail about xml_schema_flat/ and brex.xsd is dense but earns its place by specifying exactly what is inspected.

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 zero-parameter diagnostic listing tool with no output schema, the description is largely complete: it explains what is listed (schema folders), what is read from brex.xsd (the issue), what names are available, and when to use it. A minor gap remains around output format or empty-result behavior.

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?

The tool has zero parameters, so the baseline is 4. The description does not need to explain parameters because none exist.

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 uses a specific verb+resource ('Show which S1000D XML schema folders ... were found under S1000D_SPEC_DIR') and adds concrete diagnostic details about brex.xsd and schema names. It does not explicitly distinguish itself from sibling tools like validate_schema or verify_csdb, so it falls short of a 5.

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?

It gives clear usage context: 'Use it to diagnose schema-not-found results.' That tells the agent when this tool is appropriate, but it does not name alternatives or say when not to use it.

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

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

With no annotations, the description carries the full burden and discloses meaningful behavior: XSD resolution from xsi:noNamespaceSchemaLocation, lookup under xml_schema_flat/ beneath S1000D_SPEC_DIR, issue detection from brex.xsd, libxml2 error format with line/column, and a schema-not-found return case. It does not describe success return shape or any limitations beyond schema availability.

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?

Three front-loaded sentences with no filler; the key purpose and schema-resolution rule come first, followed by error format and an edge case. Minor density in the second sentence but overall efficient.

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 validation tool with no output schema, the description explains error message format and the schema-not-found case, but does not describe what a successful validation returns (e.g., valid/invalid flag, count of errors, or full result shape). That is an important omission for an agent invoking the tool without an output schema.

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 coverage is 100%, so the schema already documents all four parameters. The description adds only marginal context beyond the schema (e.g., how the issue interacts with schemaLocation inference), but does not meaningfully elaborate on xml vs. path or maxErrors beyond what the schema provides.

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 clear verb (validate), resource (one document), and scope (against the S1000D XML schema identified by xsi:noNamespaceSchemaLocation). It does not explicitly name or contrast with sibling tools like verify_data_module or list_schemas, so it falls short of full sibling differentiation.

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 when to use it (XSD-based validation of a document), but provides no explicit when-to-use vs. alternatives guidance, no exclusions, and does not mention the sibling verify_data_module or other checkers.

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

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the three verification steps being run (schema, BREX, references), that CSS-skipped steps report as "not-run" (per schema), the pagination model, and the file-writing side effect of reportPath with the reduced response. It does not state read-only safety explicitly or cost/latency expectations for large folders.

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?

Three dense sentences with the what/scope front-loaded, then paging, then the reporting side effect — no filler. The "etc." after publication modules is the one piece of avoidable vagueness.

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?

No output schema exists, yet the description tells the agent what comes back (one status per object plus valid / XSD error / BREX violation / unresolved reference / unreadable totals), which is what an agent needs to decide whether to page or write a full report. Missing only the default-folder provenance note (S1000D_CSDB_DIR) and any guidance on result size.

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 coverage is 100%, so baseline is 3. The description adds meaning for offset/limit and reportPath (response keeps only statuses), but its phrase "data modules by default; optionally publication modules etc." slightly conflicts with the schema's stated default of include=[dm, pm], which is a small source of ambiguity rather than added clarity.

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 (verify) and a specific resource scope (every CSDB object found in the given folders), and names the output shape (one VerificationStatus per object plus category totals). It implicitly distinguishes itself from verify_data_module / check_references by verifying a whole folder of objects, but never names those siblings to make the routing explicit.

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?

It gives concrete operational guidance (use offset/limit to page, pass reportPath to persist the full report), which is useful. But it never says when to use this versus validate_schema, verify_data_module, or check_references — an agent must infer the batch-vs-single and whole-object-vs-single-check distinction on its own.

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

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

With no annotations, the description carries the load and does well: it discloses that XSD validation uses the user's own schemas via S1000D_SPEC_DIR, that BREX runs along the brexDmRef chain, that skipped steps report state 'not-run', and that the tool does not judge conformance. It stops short of stating that all operations are read-only or how failures are surfaced across steps.

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?

Three dense sentences, front-loaded with the object and the check list, closing with the scope exclusion. Nothing is redundant with the schema and every clause earns its place.

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 7-parameter, no-output-schema tool the description still says what comes back: a VerificationStatus plus per-step details, and that skipped steps appear as 'not-run'. The main gap is that the possible status values and the shape of per-step details are left unspecified, which matters given there is no output schema.

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 coverage is 100%, so baseline is 3; the description still adds value by explaining that BREX and referenced modules are resolved from S1000D_CSDB_DIR and S1000D_SPEC_DIR, and by clarifying the BREX-along-brexDmRef-chain behavior that motivates csdbDirs. It adds chain semantics rather than repeating per-parameter text.

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 (verify one S1000D data module) and enumerates the four checks performed: well-formedness, XSD against the user's own schemas, BREX along brexDmRef, and reference resolution. The final clause ('Does NOT decide S1000D conformance') fences the scope off from siblings like verify_csdb, so an agent can place it without opening the schema.

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 'one data module' framing implies single-artifact use versus the CSDB-wide verify_csdb, but no sibling is named and there is no explicit statement of when to call validate_schema or check_references instead of this composite. Usage is inferable from overlapping sibling names rather than stated.

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