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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds that identity derives from sign-in or API key, which explains why no arguments exist and why the result depends on the credential, but says nothing about failure modes when the connection is unauthenticated.

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 short sentences, front-loaded with what is returned and followed by the one actionable use case. No filler or restatement of the title.

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 no-argument, read-only identity probe with no output schema, the description covers what comes back and how identity is determined. Slightly more on the returned fields or an unauthenticated-connection caveat would make it complete.

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?

Zero parameters, so there is nothing to document; the description nonetheless explains that identity is inferred from the connection's credential rather than passed in, which justifies the empty schema.

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?

Names the resource returned (the agent the current connection authenticates as) and distinguishes it from the id-based sibling get_agent by tying it to 'this connection' and its credential. It stops short of an explicit verb+object phrasing or a direct 'not get_agent' contrast, so it is clear but not fully disambiguated.

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?

One concrete use case is given: 'check the connection works.' There is no guidance on when to prefer get_agent for a specific agent id, nor any statement of what it does not cover, leaving the sibling choice to inference.

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