get_authorized_user

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

No annotations are provided, so the description carries the burden. 'Get' implies a read operation with no destructive side effects. However, it doesn't disclose what profile fields are returned, whether auth failures have specific behaviors, or if there are rate limits. For a zero-parameter read tool, this is adequate but minimal.

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?

A single sentence that fully and accurately describes the tool's purpose. Zero waste, perfectly scoped. Front-loaded with the verb immediately.

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 zero-parameter read operation with no output schema, the description is essentially complete. It tells the agent exactly what this does. The only minor gap is not describing the shape of the returned profile, but without an output schema that's a reasonable omission for such a simple tool.

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 0 parameters, so there is nothing for the description to explain. The baseline for 0 parameters is 4. The description correctly indicates no parameters are needed by not mentioning 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 'Get the currently authenticated user's profile' clearly states the verb (get) and the resource (currently authenticated user's profile). It's specific and unambiguous. It doesn't distinguish from siblings, but among ~140 sibling tools this is fairly unique since none others reference the authenticated user directly.

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 implies usage context - this retrieves the profile of the logged-in user. It doesn't explicitly state when to use this vs alternatives, but there are no obvious alternative tools that serve this same purpose. The context is clear enough that an agent would understand when to call this.

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