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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond a content inventory — nothing about return format, size, caching, or whether the manifest is static, which matters for an agent deciding whether to call it repeatedly. Appropriate at 3 given the annotation coverage.

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?

Two sentences, front-loaded with what the tool returns and ending with the when-to-use instruction. The mid-sentence enumeration of six content categories is informative but slightly list-heavy for the value it adds.

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?

No output schema exists, so the description carries the burden of indicating what is returned, and listing row types, directives, segments, tokens and paper sizes does that adequately for a zero-parameter reference tool. Minor gaps remain about format and reuse, but nothing essential for correct invocation is missing.

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 takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The content enumeration loosely maps to what callers will need, but no parameter semantics are required.

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 names the specific resource (TrMD format spec and capabilities manifest) and enumerates its contents (row types, block directives, segments, property tokens, paper sizes), so an agent knows exactly what comes back. It stops short of an explicit verb, resting on a noun phrase, but it is clearly distinguishable from every sibling tool since none other retrieves the format spec.

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?

"Read this before reading or authoring documents" gives a concrete trigger condition and ordering relative to the sibling read/write tools. It does not need alternatives because no other tool serves this purpose, but it also doesn't state what happens if it's skipped.

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