select_text

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that a range is selected, but does not explain coordinate semantics, whether positions are zero- or one-based, whether the selection replaces existing selection state, or what happens on invalid coordinates.

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 compact and front-loaded with the primary purpose, followed by a clean parameter list. There is no fluff or repeated schema information beyond what is useful given the lack of schema descriptions.

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?

Despite having an output schema so return values do not need explanation, the description is incomplete for a 7-parameter selection tool. It lacks a working example, coordinate conventions, prerequisite document state, and guidance on how the end coordinates relate to the start coordinates.

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 0%, so the description must compensate for the bare parameter titles. It adds only minimal restatement ('Start paragraph number') and one useful note that doc_id comes from open_document. The coordinate system and relationship between list/para/pos are not clarified.

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 opening line, 'Select a text range by start/end coordinates,' names a specific verb, resource, and mechanism. It is clearly about selecting a range rather than searching, inserting, or deleting text, though it does not explicitly differentiate itself from related selection/cursor siblings.

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 about when to use this tool versus set_cursor_position, get_selection_info, clear_selection, delete_selection, or get_selected_pos_by_set. The arg list explains what each parameter is, but not the circumstances in which select_text is the right choice.

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