timeiq_whoami

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get', implying read-only operation with no side effects. However, it does not specify whether any authentication is required beyond being authenticated, nor does it detail the response structure. For a simple read tool, this is adequate but not rich.

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, clear sentence that directly states the tool's purpose without any unnecessary words or repetition. It is well structured and front-loaded with the action and resource.

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 no parameters and no output schema, the description should ideally explain what 'profile and settings' includes (e.g., name, email, preferences). While it provides a general idea, it lacks specificity about the return value or any possible error conditions. It covers the basics but is not fully 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?

The tool has zero parameters, so the description correctly has no parameter info. Per the guidelines, 0 parameters gives a baseline of 4. The description adds value by explaining what the tool returns (profile and settings), which compensates for the lack of parameter detail.

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 clearly states the action 'Get' and the resource 'profile and settings of the currently authenticated acting user'. It distinguishes this tool from siblings by focusing on the current user's identity, as opposed to creating or managing other entities like clients, invoices, or projects.

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 does not explicitly state when to use this tool versus alternatives, but the context is implied: it is the tool to retrieve own profile info. Since it has no parameters and a straightforward purpose, the usage is clear enough, but explicit guidance on when not to use it (e.g., when needing another user's profile) is missing.

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