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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that — the name-vs-label distinction, the 10-minute propagation delay for published dimensions, the dryRun/confirm publish flow, and polling computeStatus until COMPLETED. Much of this, however, describes side effects of other tools rather than this read call, so it is context rather than disclosure about get_context itself.

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 purpose and the 'call first' directive are correctly front-loaded, but the body sprawls into operating instructions for at least five other tools (search, list_dimension_candidates, publish_label_dimensions, list_metrics, virtual-dimension publishing) plus column/gap-filling guidance. Those sentences do not earn their place in this tool's definition and bury the actual contract.

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?

There is no output schema, so the description must describe returns — and it does, naming dimensions with name/label, recent dashboards, externalMetricIntegrations, and a per-integration schema with DATE/NUMERIC columns. For a single-optional-param read tool the core is complete, though the parameter's auto-detection behavior is left entirely to the schema.

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?

There is one optional parameter (slug) with 100% schema description coverage, so the schema already carries the meaning, including the multi-org failure mode. The description adds nothing about slug, which is acceptable under the baseline-3 rule but earns no uplift.

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 with concrete scope: 'Get workspace context: popular groupBy dimensions, recent dashboards, and connected external-metric integrations (e.g. Tsuga, BigQuery, Datadog, CloudWatch).' An agent can immediately distinguish this from siblings like search, list_metrics, or list_dimension_candidates because the description names those as separate destinations.

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?

Explicitly says 'Call this FIRST at the start of every conversation,' which is an unambiguous trigger. It also routes the agent onward with conditions: use search with type:["dimensions"] for CEL field discovery, list_dimension_candidates for unmodeled billing keys, and list_metrics with includeExternal:true when externalMetricIntegrations is non-empty.

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