Get Profile

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

Annotations already declare readOnlyHint=true, and the description aligns with that by saying 'Get.' The description adds useful scope context ('currently authenticated user') but does not describe return format, profile field content, or authentication failure behavior. This is acceptable given the annotation coverage, but not especially 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, front-loaded sentence with no wasted words. It clearly communicates the action, target resource, and scope without redundancy or 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 simple zero-parameter, read-only tool with no output schema, the description is adequately complete. It names the resource, scope, and authentication context. It could optionally mention what profile information is returned, but this is not essential for a getter of this simplicity.

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 and schema coverage is 100%, so the schema fully describes the input surface. The description adds relevant context by clarifying that the profile belongs to the current authenticated user, which is meaningful despite the empty schema.

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 states a clear verb and resource: 'Get the profile' of the 'currently authenticated user.' It distinguishes this from sibling tools like get_user or list_accounts by specifying the self-scoped, authenticated-user context.

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 phrase 'currently authenticated user' gives clear context for when to use this tool: when you need the caller's own profile rather than a specific user's profile. It does not explicitly name alternatives or exclusions, but the self-scope is a strong implicit guideline.

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