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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds a genuine behavioral invariant beyond the structured fields — every connection maps to exactly one account, hence no id is ever accepted or required.

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 tight sentences with no filler; the payload (what is returned) is front-loaded and the no-id rationale follows as supporting context.

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?

An output schema exists, so return values need not be spelled out, and the description still summarizes the shape (account plus your role). Nothing essential is missing for a zero-parameter read, though it does not mention failure modes such as an unauthenticated connection.

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?

There are zero parameters, which establishes a baseline of 4. The description reinforces this by explicitly explaining why no account id parameter exists, making the empty schema semantically clear rather than merely empty.

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 verb and resource ("Get the Timequip account this connection is linked to, plus your role in it"), so the agent knows exactly what is returned. It does not, however, differentiate itself from siblings such as get_my_profile or get_dashboard, which plausibly touch the same account/identity domain.

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 implied rather than stated: it explains that no account id is needed because the connection is bound to one account, which is a useful precondition. But there is no explicit when-to-use guidance or routing away from related tools like get_my_profile.

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