google_gmail_status

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

No annotations are provided, so the description carries full burden. It fails to disclose behavioral traits such as whether the tool throws errors for disconnected state, whether it performs a network check, or what side effects occur. This is insufficient for an agent to understand the tool's behavior.

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 extremely concise (five words), which is good for brevity, but it sacrifices necessary detail. It qualifies as minimal viable but not optimally structured because it lacks any elaboration on return values or behavior.

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?

Given the tool has no parameters, no output schema, and no annotations, the description is the sole source of context. It fails to specify what 'connected' means, what the tool returns (e.g., boolean, status string), or any edge cases. This leaves the agent underinformed for safe 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 has zero parameters, so schema coverage is 100%. The description adds meaning beyond the empty schema by stating the tool's purpose. While 'connected' is somewhat vague, it provides enough semantic context for a tool with no inputs.

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 'Check if Gmail is connected' clearly states a specific verb ('check') and resource ('Gmail connectivity'). It distinguishes from siblings like 'google_gmail_connect' which implies an action to establish connection. However, it lacks detail on what 'connected' means in this context.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not suggest checking status before connecting or after actions. The absence of usage context reduces its helpfulness for an AI agent deciding tool invocation.

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