get_grabbed_elements

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

The description explicitly states the tool reads without deleting, contradicting the annotations which set destructiveHint: true and readOnlyHint: false. This is a serious inconsistency that misleads about tool behavior.

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 with no fluff. The first sentence front-loads the core purpose, and the second provides essential context about the batchCommit signal. Every sentence 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?

Given the simple input schema (1 optional param), no output schema, and the presence of annotations, the description covers the tool's purpose and key concept. Minor gap: no mention of return format or timeout expiration behavior, but still sufficient.

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 schema describes timeout_ms as an optional integer. The description adds the phrase 'optionally waiting up to timeout_ms', clarifying the parameter's role beyond the schema. With 100% schema coverage, this adds meaningful context.

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 specifies the verb 'Read' and the resource 'newly sent grab selections', clearly distinguishing the tool from siblings like start_grab_session and get_grab_layers. It explains the action precisely.

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 usage context (reading grab selections without deletion) but does not explicitly state when to use this tool versus alternatives or provide exclusions. No comparative guidance.

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