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

Read-only, closed-world, non-destructive annotations already cover the safety profile, so the description only needs to add capability semantics, which it does by naming the exact permission being queried. It stops short of stating the return shape (a yes/no flag) or what conditions make the answer false, which would matter for a check tool with no output schema.

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?

One short sentence, front-loaded with the capability being checked and free of padding. It reads as a noun fragment rather than a statement of what the call returns, but nothing is wasted.

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 zero-parameter check with no output schema, the description should say what comes back and how to act on it; 'whether' hints at a boolean but never states the return form or the relationship to 'open_task_editor'. Adequate to identify the tool, thin for deciding how to use its result.

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?

The tool takes zero parameters and the schema is fully described, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter context is needed or missing.

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 identifies a specific capability question — whether the current connection is permitted to open the embedded task editor — which is more informative than the name alone. It doesn't mention the obvious sibling 'open_task_editor', so an agent must infer that this is a precondition check rather than the act of opening.

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?

Usage is only implied: the phrasing suggests a gate to consult before opening the editor, but there is no explicit 'call this before X' or 'do not use this to actually open the editor' guidance despite a rich sibling set. No exclusions or alternatives are named.

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