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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's added value is the key behavioral fact that this resolves the connection's own authenticated actor rather than an arbitrary user, and that it is a cheap prerequisite call. It stops short of saying what happens when the connection is unauthenticated or what an empty/error result looks like.

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, zero filler, and the payoff (what you get back) is front-loaded ahead of the usage instruction. Every clause earns its place.

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 parameterless read of one object, the description is sufficient: it names the returned fields, which substitutes for the absent output schema, and the annotations carry the safety and idempotency profile. Nothing an agent needs in order to call it correctly is missing.

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, which is the baseline-4 case. The description adds the useful implicit signal that no identifiers need to be supplied because the actor is derived from the connection itself.

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 (return) and a precisely bounded resource: the Approveit identity 'this connection acts as', enumerating the fields returned (name, email, role, department, team). The phrase 'this connection acts as' separates it from search_team_users, which looks up other people, so an agent can distinguish the two without opening either schema.

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?

Gives an explicit trigger — 'when you need to know who "I" or "me" refers to in a request' — plus ordering guidance ('call this first'). It does not name the sibling to use for looking up another user's identity, so the when-not side is only implied.

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