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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety and repeatability profile is covered by structured data. The description adds that the return value is a static spec/manifest rather than live document state, which is useful, but it says nothing about authentication needs or payload size.

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, zero waste. The content enumeration comes first so the agent knows what it is looking at, and the actionable directive (read before authoring) is placed last where it reads as a conclusion.

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?

With no output schema and zero parameters, the description correctly carries the burden of conveying what comes back, and the content enumeration does that adequately. It could be marginally stronger by indicating the rough shape or volume of the manifest, but for a read-only reference endpoint it is complete.

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 there is nothing for the description to disambiguate; baseline 4 applies. The parameter-free nature is consistent with a pure reference lookup.

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 exactly what the tool returns — the TrMD format spec and capabilities manifest — and enumerates its contents (row types, block directives, layout directives, segments, property tokens, paper sizes). It reads as a content list rather than a crisp verb+resource, but it clearly separates this reference tool from the action siblings (traceable_doc_read, traceable_block_write, etc.).

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 an explicit, prescriptive condition for when to call it, which is stronger than most tool descriptions. It stops short of naming specific alternatives or stating when not to use it, so it is not a full 5.

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