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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds a meaningful caveat — that returned prose is not 'executable doctrine' — which is genuinely extra behavioral context. However it gives no detail on what a locator or review status actually contains.

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?

It is a single compact sentence, which is efficient, but its compactness comes at the cost of clarity rather than from tight, front-loaded substance. Minimal waste, but also minimal signal.

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 an output schema present, return structure need not be explained, but the description still leaves the core purpose and the meaning of the single parameter underspecified. For a lookup tool amid many citation-related siblings, the definition is too thin to guide a correct call.

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?

There is one required 'topic' parameter with 0% schema description coverage, so the description must compensate, yet it says nothing about what a 'topic' is, its format, or examples. The phrase 'chart topic' implies domain scope but adds no usable specificity.

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 is abstract and jargon-heavy ('book-section locators', 'rule-review status', 'executable doctrine'). It gestures at returning sourced citations with review metadata, but never plainly states the verb+resource, e.g. 'returns source references and review status for a given chart topic.' An agent cannot cleanly distinguish it from siblings like get_rule_citations or search_source_passages.

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?

No when-to-use or when-not-to-use guidance is given, and none of the close alternatives (get_rule_citations, search_source_passages, search_reviewed_rules) are named. The agent must infer usage purely from the abstract phrasing.

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