sheets_session

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

No annotations provided. The description only gives example action strings without explaining behavior, side effects, permissions, or what happens on execution. Completely opaque.

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 line, which is concise, but it sacrifices clarity. It lists commands without explanation, making it under-informative.

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?

For a tool with one parameter and no output schema, the description fails to explain the tool's purpose, valid input format, and relationship to siblings. Incomplete.

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?

The only parameter 'action' has no schema description (0% coverage). The description hints at possible values via examples, but the format is unclear (e.g., quotes, slashes). It partially compensates but remains ambiguous.

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 lists example actions like 'new "Title"' and 'open ./file' but does not clearly state what the tool does. It is ambiguous whether this tool executes session operations or lists commands. No verb+resource clarity.

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 on when to use this tool versus siblings (sheets, sheets_query, sheets_help). No indication of appropriate context or alternatives.

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