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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds one useful behavioral note: 'privacy-filtered project metadata', which tells the agent the output respects privacy filters. This is a modest addition beyond the annotations, but it doesn't disclose what the overview includes, how it's filtered, or any response characteristics. With annotations covering the core safety aspects, a 3 is appropriate.

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 a single sentence, which is concise and front-loaded with the verb, but it is concise at the expense of content. It wastes no words but also conveys little useful information. There's no fluff, but it's not sufficiently informative to earn a higher score.

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?

The tool has no output schema, so the description is the only source for what the tool returns. It does not explain what a 'context overview' is, what data it includes, or how the three optional parameters affect the result. With no output schema and no parameter semantics, the description is incomplete for an agent to call this correctly and interpret 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 description coverage is 0%, so the description must compensate by explaining the parameters, but it does not. projectId, sessionId, and executionId are listed in the schema with patterns and lengths, but the description offers no meaning, purpose, or usage hints for any of them. The agent is left to infer what 'context overview' needs these identifiers for, which is a significant 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 states a verb ('Read') and a resource ('hosted get context overview'), but the resource is itself ambiguous – 'context overview' is not defined, and the phrase 'hosted get context overview' reads like a product label rather than a functional description. It does not differentiate from many context-related siblings like get_context_graph or context_read, and leaves the agent guessing what the overview contains or how it differs.

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?

There is no guidance on when to use this tool versus alternatives. With a large sibling list including context_read, get_context_graph, project_read, and get_project_health, the description offers no situational triggers, exclusions, or comparisons. An agent cannot infer whether this is the right tool for a given task.

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