feedbin_check_auth

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

No annotations are provided, so the description carries the burden. It does convey via 'GET' that this is a non-mutating read, but it does not state whether the call raises an error or returns a boolean/status on invalid credentials, nor anything about side effects or rate limits. Adequate but not rich.

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?

A single front-loaded sentence with no filler. It would be hard to say less while still identifying the operation and the underlying endpoint.

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 check with an output schema present and 100% schema coverage, the description covers what the tool does and where it maps. The only missing piece is failure behavior, which the output schema likely partially resolves.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Nothing in the description misleads about 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?

States a specific verb and resource ('Check Feedbin credentials') and pins it to the exact endpoint (GET /v2/authentication.json), so an agent knows precisely what is verified. It is unambiguous, though it lacks explicit contrast with sibling tools (which is mostly unnecessary since no sibling does auth checking).

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?

Usage is only implied: an agent can infer this is the credential-validation call, but the description never says when to call it (e.g., before a batch of operations, after a credential error) or what to do with an invalid result. No alternatives exist to name, so the gap is modest but real.

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