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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false), so the description is free to add non-annotation context: result ordering (newest first) and the connection-level visibility/scope rule. Those are real behavioral facts an agent cannot derive from the schema. It omits pagination or result-size behavior, which keeps it below 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?

Two short fragments with zero filler, and the most important fact (what is returned and in what order) is front-loaded ahead of the parameter conditional. Nothing could be removed without losing information.

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 one-optional-parameter read tool with no output schema and full annotation coverage, the description supplies scope, ordering, and the omit-parameter behavior — enough to call it correctly. The only gap is any hint about result volume or pagination for the all-workspaces case.

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 100% and the schema already says workspaceId comes from list_workspaces, so the baseline is 3. The description goes further by explaining the semantics of omitting the parameter (fan-out across every workspace the connection can use), which is meaning the schema does not convey.

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 the resource (roadmaps), the visibility scope ("you can see"), and the ordering ("newest first") in a single compact phrase, which is enough to distinguish it from the singular get_roadmap. It never uses an explicit verb like "list", but the plural resource plus ordering makes the operation unambiguous.

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 clause "Without workspaceId: every workspace this connection can use" gives a concrete condition for the no-parameter case, which is genuine usage guidance for the only decision an agent must make here. It stops short of naming an alternative (e.g. get_roadmap for a single roadmap) or stating when to prefer the scoped call, so guidance is implied rather than explicit.

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