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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing the output boundary — only this connection's own scopes and app name, no account or menu data — which tells the agent not to expect broader context.

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 sentences with no filler: usage conditions first, then the return boundary. Every clause carries information an agent would otherwise have to infer, and nothing is repeated from the annotations or schema.

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-argument, read-only status probe, the definition covers the only open questions: when to call it and what it will and will not reveal. With an output schema present and annotations covering safety, no further detail is needed for correct invocation.

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, so the baseline is 4; there is nothing for the description to clarify beyond confirming the call is argument-free, which the empty schema already makes evident.

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 (check this connection) and explicitly bounds the payload: 'returns only this connection's own permissions (scopes) and app name, with no account or menu data.' That negative scoping clearly separates it from the menu-oriented siblings such as get_menu and list_menus.

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 concrete triggering conditions: 'once right after ChefBear is connected, or when the user asks whether ChefBear is connected or what it may do.' The 'once' wording also implies it should not be polled repeatedly. It stops short of naming an alternative tool or stating explicit when-not cases, so it falls just below the top band.

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