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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds minimal behavioral context beyond reiterating the read nature and the authentication scope. It does not contradict annotations and provides a small extra detail about the connection, but nothing substantial.

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, concise sentence with no filler. It front-loads the action and resource, and the qualifier 'represented by the current authenticated connection' adds precision without bloat.

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 simple read-only tool with no parameters and an output schema (which likely defines the profile structure), the description is fully sufficient. It states what is returned (the profile) and the context (current authenticated connection), leaving no gaps for an agent to call it correctly.

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?

There are zero parameters, so the description does not need to explain any. The baseline for 0 parameters is 4, and the description appropriately avoids unnecessary parameter information, leaving the schema to handle any future additions.

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 uses a clear verb 'Get' and specifies the resource 'Chasync user profile', further narrowing it to 'the current authenticated connection'. It is distinct from sibling tools which target other entities like forms, funnels, or leads, so an agent can easily identify this as the profile retrieval tool.

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?

While it does not explicitly state when to use it vs alternatives, the tool is the only one dealing with the user profile, and its purpose is self-evident. The description implies its usage context (retrieving the connected user's profile) without ambiguity, though it could be more explicit about when not to use it.

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