word_session_snapshot

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

Declares 'Read-only' upfront, indicating no destructive side effects. Also explains the fallback behavior with session_id. Given no annotations, the description provides necessary behavioral context, though it could mention any permissions or rate limits.

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?

Two sentences, front-loaded with 'Read-only.' No wasted words; every sentence adds value. Ideal 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?

Lacks output schema and does not describe the return format or structure of the snapshot. While it specifies it is a 'content-control snapshot,' more detail (e.g., JSON array) would improve completeness for an 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?

Only one parameter (session_id) with 0% schema description coverage. The description compensates fully by explaining its optionality and default behavior ('If session_id is omitted, uses the most recently active session.'), adding essential 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?

Clearly states 'Return the latest content-control snapshot for an open Word session.' Verb and resource are specific, and the description distinguishes it from siblings like 'word_session_read_content_control' by focusing on the full snapshot.

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?

Explicitly says 'If session_id is omitted, uses the most recently active session,' providing clear guidance on parameter usage. However, it does not mention when not to use this tool or alternatives beyond implicit differentiation.

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