word_session_read_content_control

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

No annotations provided. Description states 'read-only' but lacks details on session requirements, error states, or what happens if tag not found. For a tool with no annotations, this is insufficient.

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?

Single sentence, no extraneous words. Front-loads 'read-only' and action. Efficient.

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 4 parameters, 0% schema coverage, and no output schema, the description is too brief. Lacks details on parameter meaning, return values, and prerequisites.

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%, but description only mentions 'tag' implicitly. No explanation of wait, session_id, timeout_seconds. Parameters are not documented beyond schema.

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 reads content-control text from an open Word document by tag, using Office.js taskpane. It distinguishes from file-based tools like docx_read_content_control.

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 read-only usage and mentions 'by tag', but does not explicitly state when to prefer this over siblings or conditions to avoid. Some context from sibling names hints at live document vs file.

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