Verify Crown Town Compost auth + connectivity

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description reinforces read-only behavior and adds useful context by specifying error classification ('no creds' vs 'bad creds' vs 'site error') and the exact fields reported. This goes beyond what annotations provide.

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, information-dense sentence that front-loads the main purpose ('Confirm credentials are configured') and efficiently covers steps, output, and error handling. It is not bloated, though it could be broken into two sentences for readability. Every clause 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?

For a healthcheck with no input and no output schema, the description covers what it does, what it returns, and error classification. It also states read-only behavior. It doesn't mention rate limits or auth prerequisites beyond credentials, but these are minor given the tool's simplicity and the annotations already covering safety.

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 the description need not explain any parameter meaning. Baseline for 0 params is 4. The description adds nothing about parameters (as none exist) but does describe output shape, which is not directly relevant to this dimension.

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 ('Confirm', 'log in', 'fetch', 'report') and resource ('Crown Town Compost portal'), and clearly differentiates it from siblings by framing it as a healthcheck. It explicitly lists the output fields, so an agent can instantly see it's a diagnostic tool, distinct from get_dashboard or get_account.

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 implies its usage for verifying credentials and connectivity but does not explicitly state when to use it versus alternatives like crowntown_get_dashboard or crowntown_get_account. There is no 'use when...' or 'don't use when...' guidance, though the purpose is self-evident from the title and description.

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