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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the contextual constraint that this is a 'closed' family bound to the 'frozen Brain Scanner policy,' but it does not explain operational behaviors such as pagination, failure modes, or scope of returned data.

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 short sentence, so it is not verbose. However, the sentence spends most of its length on policy jargon ('closed... frozen Brain Scanner policy') rather than useful tool semantics, making it concise but under-informative.

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?

This is a complex tool with six discriminated operation variants and no output schema, so the description must carry substantial explanatory weight; it does not. An agent cannot determine which operation fits a scenario, what results look like, or how errors are surfaced from this description alone.

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%, and the description provides no param-level meaning beyond what the schema's operation enum and payload constraints already show. It does not clarify when to use get_pending_implementation_meter_changes versus relay_poll, or what values like cursor/limit mean in context.

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 says to 'Use the closed workflow read capability family,' which communicates read-only intent but never names a concrete resource or operation set. It essentially restates the tool name with 'capability family' and does not distinguish workflow_read from context_read, project_read, or graph_read.

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 about when to invoke this tool instead of other read tools, nor about which of the six oneOf operations to select for a given task. The imperative 'Use...' provides no eligibility criteria, preconditions, or exclusion conditions.

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