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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real context beyond them: lists return metadata only with a `nextOffset` cursor, reads return the full method body in a single call, and scope/approvals constraints still apply. It stops short of describing what the body or metadata contain or what happens on an unknown key, which is why this is a 4 rather than a 5.

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?

Front-loaded with the action and the preferred path, and each sentence carries operational content (route keys, pagination, mandatory method use). The closing MCP boilerplate about the input object and structured content is generic padding, and the credit-cost note is useful but sits after the payload rather than near the top.

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, no-output-schema tool with a nested input object, the definition covers modes, pagination, scoping, and approval caveats — enough to invoke it correctly. The main residual gap is that return shape (what metadata vs. full body look like) is only hinted at, which matters given there is no output schema to fall back on.

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 75% and the schema already documents `offset` and `command`, but not `query` or `skillId`. The description fills that gap by explaining the query→skillId handoff and clarifying that `command` is an exact installed method key scoped to the current source. It does not cover the nested `accountIds`/`userStatement`/`idempotencyKey` fields at all, leaving that gap to the schema.

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?

Opens with a specific verb+resource+timing: 'Choose and read a workspace method before specialist work.' It then names the two concrete modes (command key read vs. query search then skillId read) and gives example route keys (budget-pacing, unit-economics, revenue-reconciliation), so an agent knows exactly what this returns versus any other tool in the list. No sibling overlaps on method retrieval, so sibling differentiation is effectively satisfied.

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?

Gives an explicit decision rule: prefer `command` when the route key is known to load the body in one call, otherwise search with `query` and read a returned `skillId`. It also pre-empts a likely wrong inference by stating that strategic proposals, read-only plans, and 'do not launch' requests STILL REQUIRE their method — that is a when-not-to-skip rule, not just a when-to-use one.

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