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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: it requires auth credentials and costs nothing, and it itemizes what the response exposes. It stops short of saying what happens when unauthenticated or whether any of the disclosed secrets (API key, sign-in link) are truncated.

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 sentences plus two fragments, with no filler, and the account identity is front-loaded. The long field enumeration earns its place because there is no output schema and the fields are the return contract, though the trailing 'Free. Needs the user's...' fragments are telegraphic rather than well-integrated.

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?

With no output schema, the description carries the burden of describing the response, and it does so thoroughly by listing every category of data returned. Auth requirement and cost are also stated, leaving only edge-case behavior (missing credentials, secret masking) unspecified, which is minor for a parameterless read.

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; the schema is a closed empty object with 100% coverage. Baseline 4 applies, and the description correctly spends no words on argument semantics.

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 names a specific resource, the Cotlet account this connection acts as, and enumerates exactly what is returned: email, workspace, access status, key/OAuth client and scope, permitted apps, credit balance, and signup app with first task and sign-in link. That is concrete enough to distinguish it from narrow siblings such as cotlet_balance or cotlet_apps, though it frames the tool as a noun phrase rather than stating a verb like 'returns' or 'reports'.

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?

It supplies a prerequisite ('Needs the user's Cotlet API key or sign-in') and a cost note ('Free'), which help an agent decide whether it can be called. It does not say when to prefer this over the more specific siblings (cotlet_balance, cotlet_apps), so usage is only implied by the breadth of the returned fields.

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