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

With no annotations, the description still discloses the important behaviors: the 6000-character default body, that offset/next_offset count characters within the selected body, that continuation should happen only for requested missing text, and that full=True is reserved for explicit downloads. It is silent on what happens with an unknown anchor or slug and on any rate/permission constraints, which keeps it short of a 5.

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 purpose and the shortcut relationship come first, followed by view, pagination, and then the two routing exclusions, so an agent can stop reading once it has what it needs. It is dense with directives and slightly overpacked for a single document reader, but no sentence is filler.

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 five-parameter, zero-required read tool with no annotations and no output schema, the description covers trigger, alternatives, view selection, pagination continuation, and the full-download escape hatch. Nothing an agent needs in order to call it correctly is missing, and the absence of an output schema is offset by the paging contract described.

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?

Schema coverage is already 100%, but the description adds meaning the schema does not: which view to pick for which need, the relationship between offset, next_offset, and character counts inside the selected body, and the rule that full cannot be combined with paging and should be used only on explicit download requests. This is genuine semantic guidance, not restatement.

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 a specific verb (read) and resource (the Signals Quick Reference guide) and explicitly states it is the document-reading shortcut for kb_get_document slug=10-signals-quick-reference rather than an extra validation step. An agent can distinguish it from kb_get_document, query_knowledge, and the runtime catalogue without opening any schema.

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?

It gives an explicit trigger (user asks for that guide or its documented entries), points to view=overview for outlines and view=section with an anchor for passages, and routes two adjacent cases elsewhere: query_knowledge op=ask for conceptual combinations and the runtime catalogue for executable signal names. When-not-to-use is as clear as when-to-use.

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