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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the description doesn't need to restate those. It does add the context that the profile is 'authenticated,' implying it depends on the current auth state, but it doesn't disclose behavior like error cases or rate limits. The description is consistent with annotations, so no contradiction.

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 extremely concise with only three words, which is good for front-loading, but it's under-specified. It's a fragment rather than a complete sentence, and while it doesn't waste words, it might omit essential information for clarity. For a tool this simple, the brevity is acceptable but not exemplary.

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 the tool's minimal complexity (0 params) and the presence of annotations and an output schema, the description could be sufficient. However, it lacks usage guidance and doesn't explicitly state the operation or distinguish from similar tools. The description is complete enough for a simple retrieval but leaves some contextual gaps.

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 baseline is 4. The description doesn't need to explain parameter meaning, and the empty schema already provides full coverage. No additional semantic value is required here.

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 'Authenticated user profile' is a noun phrase rather than a clear verb+resource statement. It implies the tool returns the profile of the authenticated user, but it doesn't explicitly state what action is performed. It also doesn't differentiate from the sibling tool 'user', which may cause confusion.

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 no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, contexts, or exclusions. With siblings like 'user' and 'entity_profile', an agent needs more direction to select the right tool.

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