qms_register

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Read-only', which is a critical behavioral trait for an agent deciding whether to call this tool. It also discloses the type of output (procedure per name, overdue reviews, and Art. 17(1) aspects), giving the agent a clear expectation of what will be returned.

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 concise sentence at the top, front-loading the key information about what the tool returns. It avoids unnecessary details and is easy to parse, though the grammatical structure could be clearer (e.g., 'the ones overdue for review' is a bit awkward). Still, it is 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 zero-parameter tool with no output schema, the description covers the essential context: what data is available and that it is read-only. An agent can decide whether to call it based on the need for current QMS procedures, overdue reviews, or Art. 17(1) status. No critical missing information is apparent.

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, and the schema is empty. Per the rubric, a baseline of 4 applies when there are no parameters. The description does not need to add parameter context, and no gaps exist since there is nothing to document.

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 information the tool provides: the current QMS procedure per name, overdue reviews, and relevant Art. 17(1) aspects. It identifies the resource (QMS register) and the specific type of data, though it uses a noun phrase rather than an explicit verb like 'get' or 'list'. This is enough to distinguish it from most siblings, which focus on other compliance aspects.

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 this is a read-only reporting tool for QMS status, but it does not explicitly state when to use it versus alternatives such as record_qms (likely the write counterpart) or other compliance reports. No exclusions or alternative tool names are given, leaving the agent to infer usage from the content.

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