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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds only 'Read-only,' which is redundant with the readOnlyHint. No additional behavioral context is provided, such as authentication requirements, side effects, or output characteristics. The description carries minimal added value beyond the annotations.

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?

The description is a single sentence with no filler words. It is appropriately sized for a simple, parameterless tool and conveys its purpose in a compact form.

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?

Given that there is no output schema, the description should clarify what the tool returns. It only says 'The organization and user this connection reads for,' which does not specify the return format or content. The description is cryptic and relies heavily on the title for meaning. For a tool with no parameters, this is incomplete guidance for an agent.

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 fully documents this with an empty properties object. There is nothing for the description to add about parameters. The baseline of 4 is appropriate because there is no ambiguity to resolve.

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 states 'The organization and user this connection reads for' but lacks a clear verb like 'returns' or 'gets'. It reads as a noun phrase describing context rather than an explicit action, leaving the tool's function ambiguous. The title 'Who am I' provides some hint, but the description itself is not self-explanatory.

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?

The description offers no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or exclusions, and there is no reference to sibling tools. An agent has no basis to decide when to call this tool over others.

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