get_workspace_batch_calls

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally. The description adds nothing beyond that — no mention of pagination (implied by limit/last_doc), default limits, or ordering. With annotations doing the heavy lifting, the description still contributes no extra behavioral context.

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?

It is a single front-loaded sentence with no waste, which is structurally fine, but the brevity comes from under-specification rather than disciplined concision — there is simply very little content to organize.

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 listing tool with three parameters (two undocumented) and no output schema, the description should at minimum describe pagination behavior and what the returned batch calls represent. None of that is present, leaving the agent to guess how to page through results.

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 only 33%: agent_id is documented in the schema, while limit and last_doc are bare. The description says nothing about these parameters, and last_doc in particular reads as a pagination cursor that an agent would need explained; the description does not compensate for the coverage gap.

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?

States a clear verb and resource ('Get All Batch Calls For A Workspace'), which distinguishes it at a high level from singular get_batch_call and from mutating siblings like create_batch_call or cancel_batch_call. However, it never explains the workspace-scoping or batch-specific framing beyond restating the name, so an agent must infer the distinction from the name alone.

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?

There is no guidance on when to use this rather than get_batch_call (single batch call) or any of the other batch-call siblings. Nothing about prerequisites, workspace context, or result scope is provided.

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