reindex_doc_graph

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

With no annotations, the description carries the burden. It discloses two behavioral constraints (monthly quota and plan level) but does not describe effects of reindexing, duration, reversibility, or response. This is minimal but not entirely opaque.

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 short sentences, front-loaded with the verb and resource. Every word earns its place; no redundant 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 zero-parameter operation, the description covers purpose and constraints, but because there is no output schema and no annotations, it leaves out behavioral details like what the reindex actually changes or returns. Sufficient for a simple action but not fully 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 has zero parameters and the schema coverage is 100%, so there is no parameter gap. The description cannot add parameter meaning; baseline 4 applies.

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?

Description uses the specific verb 'Reindex' with a named resource ('Source of Truth doc graph'), clearly distinguishing this mutation tool from read-only siblings like get_doc_graph. The intent is immediately understandable.

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 implies the tool is the action to refresh the doc graph and states access constraints ('100/mo limit', 'PRO+ plan'), but it does not explicitly state when to use it vs alternatives or when not to use it. The constraint info provides useful context, but no exclusion or explicit alternative guidance.

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