tenki_list_workspace_snapshots

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds useful non-obvious behavior: the default workspace behavior and pagination support. This exceeds what the annotations alone communicate, though it does not detail pagination iteration mechanics.

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 short sentences with no filler. The main action is front-loaded, immediately followed by the default-workspace behavior and pagination support. Every word earns its place.

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 read-only, idempotent list operation with no required parameters and no output schema, the description covers the key usage context: workspace scope, default workspace, and pagination. It omits details like sorting or result shape, but these are not necessary for an agent to invoke the tool correctly. Slight gaps in pagination parameter semantics prevent a 5.

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 description coverage is only 33%, with page_size and page_token lacking any schema description. The description merely says 'Supports pagination' without explaining how page_token works, what page_size controls, or how the two interact. With low schema coverage, the description needed to compensate but does not.

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 states a specific verb and resource: 'List all snapshots in a workspace', which clearly differentiates it from session or dangling snapshot tools. The added default-workspace behavior ('defaults to the key's first workspace') makes the scope even more concrete. It does not name sibling tools explicitly, but the workspace-scoped phrasing is enough to disambiguate.

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 gives clear context: this is for listing snapshots scoped to a workspace, and it explains that the workspace defaults to the key's first workspace. This helps an agent decide when to use this tool. It does not explicitly state when not to use it versus other snapshot-listing tools, but the workspace framing provides solid guidance.

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