list_subposition_positions

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is clear. However, the description adds no behavioral context beyond the bare 'Fetch a list', missing details like pagination behavior, ordering, or the dependence on document_type/document_id that the schema implies.

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 a single sentence, but it essentially restates the tool name and provides no additional information. It is under-specified rather than efficiently concise; the sentence does not earn its place with valuable content.

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?

The tool has no output schema, so the description should account for return behavior. It does not mention that the operation requires a document type and document ID, nor what kind of data is returned. Combined with minimal behavioral context, the description is insufficient.

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 description coverage is 100%, so the four parameters (limit, offset, document_id, kb_document_type) are fully documented in the schema. The description adds no extra parameter meaning, but given high coverage, the baseline of 3 is appropriate.

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 a clear action ('Fetch a list') and a specific resource ('sub positions'), which is consistent with the tool name. It is distinguishable from 'get_subposition' by the list vs. single-item verb, but it does not explicitly mention document scope or alternatives.

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?

There is no guidance on when to use this tool versus alternatives. The description does not provide context about required document types, filtering, or scenarios where other list tools might be more appropriate.

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