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

With no annotations provided, the description bears the full burden of behavioral disclosure. It only states that it checks hash linkage for tampering, but does not clarify whether the operation is read-only, requires specific permissions, or what happens when tampering is detected. This leaves the safety and failure behavior largely implicit.

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 two short sentences with the main action front-loaded. It is appropriately sized for the tool's simplicity and contains no redundant or filler wording.

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 no annotations, no output schema, and an undocumented parameter, the description is incomplete. It explains the core purpose but omits usage guidance, parameter semantics, and behavioral context such as return format, errors, or side effects, leaving a knowledgeable agent with significant gaps.

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 schema has one required parameter (client_id) with zero schema description coverage. The tool description never mentions this parameter, providing no insight into its expected format, meaning, or constraints. The description does not compensate for the missing schema documentation.

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 states a specific action ('Verify audit chain integrity') with a clear resource (audit chain) and explains the mechanism ('Checks chain hash linkage for tampering'). This distinguishes it from other audit-related tools like audit_log or audit_query, which focus on recording or retrieving logs.

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 explicit guidance on when to use this tool versus alternatives. The verb 'Verify' implies usage for integrity checks, but the description never states when it should be chosen over siblings like audit_query or ai_provenance, nor does it mention any exclusions or prerequisites.

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