qobrix_whoami

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

With no annotations provided, the description fully carries the transparency burden. It discloses a conditional behavior (surfacing a Sign In link in Mode C without a session) and notes that OAuth subject is included when available. This goes well beyond a simple 'returns the current user' statement.

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 three sentences, each earning its place: what it returns, an edge-case behavior, and the intended use. It is front-loaded and free of filler.

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-parameter, no-output-schema tool, the description covers all essential context: the resource returned, the authentication edge case, and why to call it. It is complete for the tool's complexity.

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 input schema confirms this. According to the rubric, the baseline for 0 params is 4, and the description does not need to add parameter-level detail. It correctly avoids inventing any.

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 opens with 'Return the current Qobrix user profile, capabilities, and portals', which uses a specific verb and resource and clearly distinguishes this from sibling tools that query CRM data. It is immediately obvious what the tool does.

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?

It explicitly states 'Use to confirm which CRM identity the agent is acting as for this user', giving a clear when-to-use scenario. It also describes the Mode C no-session behavior, which implies it is relevant after authentication. It does not name alternatives, but no sibling tool serves the same purpose.

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