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

The annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by specifying exactly what is returned (account name and can_generate boolean) and reaffirms no account data changes, which is useful beyond the structured 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?

Two concise sentences with a clear when-to-use trigger front-loaded, followed by the return contract. No redundancy or filler, every sentence earns its place.

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, read-only tool, this description is complete. It conveys the invocation trigger, the read-only safety, the exact returned fields, and the lack of side effects. No additional information is needed for an agent to call it correctly.

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 and the schema coverage is 100% by default. With 0 params, the baseline is 4; the description further explains the output fields (account name, can_generate) which adds semantic understanding, even though no parameter details are needed.

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 verb and resource: returns the connected DocuWriter.ai account name and a can_generate boolean. It clearly distinguishes itself from generation-execution or other getters among the siblings by focusing on the account's connection status and generator availability.

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?

The description explicitly says 'Use this when the user asks which DocuWriter.ai account is connected or whether it can run a generator,' giving clear when-to-use conditions. It does not list alternatives or exclusions, but for a simple read-only zero-parameter tool, this is sufficient context.

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