protocol_check_compliance

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. The verb 'check' implies a non-mutating operation, but the description does not explicitly state that it leaves state unchanged, nor does it explain what 'compliance status' entails or what errors may occur. It adds some transparency but leaves room for ambiguity.

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, front-loaded sentence with no filler. It states the action and target clearly, making it concise and easy to parse.

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 no parameters and no output schema, the description should explain what the caller receives or how compliance status is determined. It does not, and it also fails to distinguish itself from the similar-looking protocol_get_session_report. The description is minimally viable but leaves gaps about output format and usage context.

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, meaning there is nothing to document. The baseline for 0-parameter tools is 4, and the description's purpose statement adds contextual meaning, even though it does not mention parameter details (as 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 the specific verb 'check' and the resource 'protocol compliance status', clearly indicating a read-only diagnostic action. It is unambiguous about the operation. However, it does not differentiate itself from the sibling tool protocol_get_session_report, which may also report on compliance status.

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?

There is no guidance on when to use this tool versus alternatives such as protocol_get_session_report or protocol_suggest_missing. The description lacks any context about prerequisites, typical invocation scenarios, or which sibling tools are better suited for specific needs.

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