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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the description is not burdened with those. It adds useful behavioral context: the call is cheap, and it returns clients with projects, aliases, and effective rates. It also notes a preference for a resource alternative. This goes beyond the annotations without contradicting them.

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?

The description is two sentences plus a brief note. It front-loads the primary purpose and usage guidance, then adds a cost hint and resource alternative. No wasted words; 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?

For a simple read-only list tool with one optional parameter, the description covers purpose, usage, and return contents. However, the include_archived parameter is completely undocumented, which is a significant omission given the 0% schema coverage. Also, the response structure is only vaguely described, though without an output schema that is somewhat expected. Overall, moderately complete but with a notable gap.

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 0%, so the description carries the full burden for the include_archived parameter. The description never mentions this parameter or its effect on the result set. An agent cannot infer from the description whether archived items are excluded by default or what include_archived=true means. This is a clear 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?

The description clearly states the verb 'list' and the resources 'clients, projects, and rates'. It explicitly names the use cases (resolving ambiguous project names, checking rates) and differentiates from sibling creation tools like workspace.create_client and workspace.create_project. The purpose is unmistakable.

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 explicit 'when to use' conditions (user asks about projects/clients/rates, resolving ambiguity before logging time) and even recommends a cheaper alternative (reading workspace://context) when supported. It implies when not to use it by contrast with the creation siblings, providing clear routing guidance.

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