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

No annotations are provided, so the description must fully disclose side effects and behavior. It states a check and possible setup guidance, but it is unclear whether 'guide setup' involves performing mutations or just providing instructions. This ambiguity is problematic for an agent that needs to know if the tool could change state.

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, efficient sentence that quickly conveys the tool's purpose. However, it crams two actions ('check' and 'guide setup') into one sentence without clear structure, making it slightly less clear than a two-sentence version would be.

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?

The tool is simple with no parameters and no output schema, but the description still leaves important gaps: it does not explain what 'configured' means, what the return value looks like, or what 'guide setup' entails. Given the lack of annotations and output schema, the agent would be under-informed about the expected behavior.

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 the description correctly aligns with that. Per the baseline for zero-parameter tools, a score of 4 is appropriate because no parameter explanation is 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 uses a specific verb 'Check' with a clear resource 'email providers' and a clear outcome ('if configured'). It also mentions a secondary action 'guide setup if needed'. However, it does not explicitly distinguish itself from the sibling tool 'test_email_config', which likely has a similar purpose, so it loses a point for lack of differentiation.

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 guidance on when to use this tool versus alternatives. The description implies a context of verifying email configuration but never mentions 'test_email_config' or other related tools, leaving the agent without clear selection criteria. No exclusions or alternative mentions are provided.

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