dms_legal_documents

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. The description does not mention whether the tool is read-only (though 'query' implies it), whether any authentication is required, or what happens if no parameters are provided (e.g., returns all 63 records?). It also omits details about pagination, rate limits, or side effects. Given the absence of annotations, the description should compensate, but it falls short.

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 concise at one sentence and front-loads the key action ('query the Documents & Records Register') immediately. It adds value without being verbose. However, it could be slightly improved by removing unnecessary specificity (e.g., the exact record count '63' might become stale, but for now it is fine).

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 tool has a moderate complexity (2 optional parameters, no output schema, no annotations), the description provides a basic level of completeness by identifying the source and scope. However, it omits guidance on usage context, behavioral traits, and how output is structured. For a tool with a specific purpose like querying legal documents, the description should explain what the returned records look like or how to interpret the 'evidence class' etc. The lack of output schema makes this gap more significant.

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 input schema has two parameters with clear descriptions: 'limit' (max rows, default 100) and 'compliance_id' (filter by string). The schema description coverage is 100%, so the schema already provides meaning. The tool's description adds context by mentioning the specific workbook and record categories, which complements the parameter meanings. However, the description could add more semantics, such as how 'compliance_id' relates to the records, but it already goes beyond just the schema.

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 what the tool does: query the Documents & Records Register, specifying the source (Legal Compliance Workbook) and the scope (63 records). It covers the key resource ('Documents & Records Register') and the verb ('query'), and it distinguishes itself from siblings by specifying the exact register and workbook. The mention of 'required evidence, retention, storage, evidence class' adds detail on the nature of the records, making its purpose distinct from sibling tools like dms_legal_requirement or dms_legal_register.

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 lacks guidance on when to use this tool versus its many siblings (e.g., dms_legal_register, dms_search, dms_list). It does not explain what makes this tool the best choice for querying legal documents or when one should prefer an alternative. There is no mention of prerequisites, limitations, or context for use.

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