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

With no annotations, the description carries the full burden, and it does well: it clarifies the tool is a read-only introspection call, takes no arguments, and returns specific information (organization and granted scopes). It doesn't describe error behavior or exact output format, but for a simple whoami-style tool, the behavioral surface is small and adequately covered.

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 with zero filler. The return-value information is front-loaded, followed by the use case, and every sentence earns its place. It is compact enough to be read quickly and complete enough to be actionable.

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-argument, read-only tool with no output schema, the description is complete: it states what the tool returns, that it takes no arguments, and the intended use case. An agent has everything needed to select and call it correctly. The absence of output schema details is acceptable because the description sufficiently describes the return domain (organization and scopes).

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 has zero parameters and the schema is already empty, so the description's explicit 'Takes no arguments' adds useful confirmation for an agent. This matches the baseline for parameterless tools: no parameter documentation burden exists, and the description reinforces the no-argument contract without redundancy.

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 ('Returns') tied to a clear resource: the organization the connection is scoped to and its granted scopes. This clearly distinguishes it from sibling tools like list_decision_changes and query_decision, which operate on decision data rather than connection/auth context. The title 'Who am I' reinforces the identity-check purpose without any ambiguity.

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?

Explicitly states when to use it: 'Use it to verify the connection and the service token.' This gives an agent a concrete trigger condition and makes the tool's role in an auth/connectivity workflow obvious. It doesn't need to exclude siblings because its subject matter is fundamentally different from the decision-related siblings.

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