flow_account_check

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the verification intention but does not describe what the tool actually returns (e.g., boolean, message), whether it is read-only, or what happens when the accounts do not match. This lack of behavioral detail is a significant gap given the absence of annotations.

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, perfectly concise and front-loaded with the main action ('Verify'). It contains no filler or redundant information. Every word contributes to the tool's purpose.

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 tool with no parameters, no output schema, and no annotations, the description provides a basic but adequate purpose. However, it lacks critical operational context such as what the tool returns, whether it is a safe read-only operation, and any failure indications. Given the simplicity of the tool, this makes it minimally viable but not fully complete.

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 input schema has zero parameters and 100% schema description coverage, so there are no parameter semantics to explain. The description adds context about the expected email (Profile 3) which clarifies the tool's purpose. The baseline for zero parameters is 4, and the description does not require further elaboration.

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 clearly states the tool verifies that the logged-in Google account matches a configured expected email. The verb 'verify' is specific, and the resource is precisely defined (logged-in Google account vs expected email). This distinguishes it from sibling tools like flow_connect or flow_status, which pertain to connections or general status rather than account verification.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention any prerequisite conditions, exclusions, or cases where another tool would be more appropriate. An agent is left to infer that this is a pre-flight check, but that is not stated.

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