get_current_user

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

Since no annotations are provided, the description carries full burden. It discloses the tool is read-only and returns profile fields including timezone, recordActions, name, etc. It does not mention destructive behavior or side effects, which is appropriate. The description is transparent about the return value and its usage.

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 well-structured with a clear main sentence followed by bullet-point usage guidelines. It is fairly long but every sentence adds value. Slight improvement could be more concise grouping, but overall effective.

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, an output schema exists, and the description thoroughly covers when and how to use the tool, it is fully complete. It provides all necessary context for an AI agent to correctly invoke and use the output.

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?

With 0 parameters, the baseline is 4. The description does not need to add parameter info, and it provides context on what the tool returns, which is sufficient.

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 explicitly states the tool's purpose: 'Get the current authenticated user's profile from Kylas (GET /users/me).' It clearly identifies the resource and action, distinguishing it from sibling tools by focusing on the returned timezone and profile fields.

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 provides explicit guidance: 'Call this whenever a date or datetime-related query is involved.' It then gives specific instructions for using the returned timezone in filtering (search_leads, search_idle_leads) and lead creation (create_lead), effectively telling when and how to use this tool versus alternatives.

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