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 only adds 'chain-linked' and 'integrity check', which hints at verification behavior but does not state whether the operation is read-only, what happens on integrity failure, or what the return format is. This is insufficient for an agent to predict the tool's side effects or error conditions.

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 extremely short (six words), which is concise and front-loaded, but it is more under-specified than effective. It omits a verb and critical behavioral context, so while it is not verbose, it fails to provide enough substance to be a genuinely useful tool description.

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 absence of annotations, output schema, and required parameters, the description is the sole source of context. It does not explain return values, pagination, error behavior, or the role of 'entity_id'. For a tool with two parameters and no output schema, this level of detail is inadequate for an agent to use it correctly without external knowledge.

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 describes 'limit' with 'Max entries', but 'entity_id' has no description, leaving its purpose ambiguous (likely a filter, but unstated). The tool description itself adds no parameter information, so the semantics of half the parameters are entirely unexplained. At 50% schema coverage, the description should compensate for the undocumented parameter, but it does not.

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 'Chain-linked audit log with integrity check' identifies the resource (audit log) and a notable property (chain-linked integrity), but lacks a verb or explicit action such as 'retrieve' or 'verify'. It is more of a noun phrase than a tool purpose statement, and while it distinguishes from many sibling tools by focusing on audit trail, it does not clearly state what the tool does.

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 provides no guidance on when to use this tool versus alternative audit/log-related siblings like 'evidence_pack' or 'evidence_summary'. There are no use-case examples, exclusions, or comparisons, leaving the agent to infer appropriate usage from the name alone.

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