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

Annotations already carry the full safety profile (readOnlyHint, openWorldHint, destructiveHint, idempotentHint), so the description's added burden is lower. The description adds a useful cost hint ('cheap') and sketches the return shape (current step + next_step), but it does not address the surprising destructiveHint=true, leaving an unexplained behavioral flag. Value added is real but modest against a rich annotation set.

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 tight sentences, front-loaded with the core summary ('Cheap flow check') followed by the output shape and the usage directive. Every clause earns its place with no filler or restated metadata.

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 and no parameters, so the description must carry the return-value burden — which it does by naming the connected-status flags and the `flow` object with current step and `next_step`. It is complete enough to invoke correctly, though the exact shape of `flow` is only described at a high level.

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 per the rubric the baseline is 4. There is nothing for the description to disambiguate, and it correctly spends no words on parameter semantics.

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 specific purpose: a status/flow check reporting whether GitHub/Vercel are connected plus a `flow` object with the current step and `next_step`. It distinguishes itself from the many sibling listing tools (list_code_sites, github_list_repos) by explicitly framing itself as a single orientation call rather than a re-listing operation. The jargon ('flow object', 'nudge') slightly muddies the verb, keeping it from a clean 5.

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?

It gives an explicit usage rule — 'Call this ONCE to orient instead of re-listing repos/sites every turn' — which tells the agent both when to use it (orientation) and what not to do (repeated listing). It stops short of naming the alternative tools by name, so an agent still has to infer which siblings this replaces.

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