section

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

No annotations are present, and the description does not disclose any behavioral traits such as whether the tool is read-only, destructive, or requires specific permissions. The parameter 'op' hints at multiple behaviors, but no further details are given.

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 description is extremely short (one sentence), which is concise but at the expense of essential information. It does not earn its place because it fails to clarify the tool's purpose or parameters.

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 12 complex parameters, no output schema, and no annotations, the description is grossly inadequate. It should explain the 'op' parameter, the meaning of each parameter, and how they interact (e.g., how path and section_id relate, what format controls, etc.).

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 input schema has 12 parameters with 0% description coverage (no parameter descriptions in the schema). The tool description adds no meaning to any parameter. For example, 'op' is required but not explained; 'doc_id', 'path', 'section_id', and others remain opaque.

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 'Consolidated section navigation entrypoint' gives only a vague sense of the tool's domain (sections and navigation). It does not specify what operations are possible (e.g., get, list, modify) nor distinguish it from sibling tools like 'document' or 'evidence'. The parameter 'op' likely indicates the action but is left unexplained.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context that would help an agent decide to invoke 'section' instead of other document-related tools.

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