word_session_wrap_selection

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

The description indicates a write operation ('Write') but does not disclose behavioral traits like destructiveness, prerequisites (e.g., required taskpane state), error conditions for missing selection, or side effects. With no annotations, the description should provide more detail.

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 very short (two brief sentences) and front-loaded with the key action. However, it sacrifices necessary detail for conciseness.

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?

Given 5 parameters and no output schema or annotations, the description is incomplete. It fails to explain return values, prerequisites, or parameter interactions, leaving significant gaps for an AI agent.

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%, yet the description only mentions 'tag/title' without explaining parameters like wait, session_id, or timeout_seconds. It does not map these to specific fields or clarify their roles, leaving the agent without necessary semantics.

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 clearly states the tool wraps the current Word selection in a content control with a stable tag/title. The verb 'wrap' and resource 'current Word selection' are specific. It distinguishes from sibling tools like word_session_read_content_control, which are read-only.

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 such as docx_apply_patchset or other document manipulation tools. The description lacks context for appropriate usage scenarios.

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