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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing what the bundle actually contains (brief, facts, links, decisions log), which matters because there is no output schema; it stops short of noting fuzzy-resolution failure modes or auth requirements.

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 tight sentences that front-load the verb and payload before the usage instruction. The trailing API reference URL is slightly extraneous but cheap and potentially useful.

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?

With no output schema, the enumeration of returned components (brief, facts, links, decisions) is the key information an agent needs to know what it gets, and the usage sentence covers invocation intent. What's missing is minor: behavior when the client name is ambiguous and how the decision_limit shapes the response.

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 67% — 'client' and 'decision_limit' are described in the schema (including fuzzy resolution and the default of 20), while 'client_id' carries only format/pattern. The description adds no parameter detail beyond that, so the baseline of 3 is appropriate.

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 specific verb and resource ('Fetch the shared context bundle for a client/workspace') and enumerates the payload: brief, structured facts, reference links, recent decisions log. This clearly separates it from siblings like get_project_context and update_client_context.

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 trigger: 'Call this before working on any task tied to a client so you inherit the same ground truth.' It doesn't state when-not to use it or name a specific alternative, but the pre-task framing is clear.

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