get-sync-status

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

Description discloses that it returns whether Mail.app is running and whether sync activity was detected. With no annotations, this is adequate for a read-only check; no side effects or contradictions.

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 no fluff. Every sentence adds value.

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 zero parameters and output schema exists, description fully explains what the tool does and its return values, plus provides usage context. 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?

No parameters; baseline 4. No additional semantics 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?

Clearly states the tool checks whether Mail.app is running and syncing, and its purpose is to explain why new mail hasn't appeared. Distinguishes from siblings by specifying not to use for message counts or full diagnosis.

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?

Explicitly provides when to use ('checking whether Mail.app is running and actively syncing') and when not to use ('need message counts' or 'full setup diagnosis'), naming alternatives (get-mail-stats, doctor).

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