Get current user profile

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint:false, so the safety profile is well-covered. The description adds the HTTP endpoint (GET /api/auth/profile) and authorization class ('board'), which provides useful implementation details beyond the annotations. However, it doesn't discuss any side effects or error conditions.

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, consisting of just two lines. It front-loads the purpose and includes the key implementation detail. Every word earns its place with no fluff.

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 has no parameters, strong annotations, and an output schema, the description is adequate. It states the operation and endpoint, which is sufficient for a simple read-only profile retrieval tool. A minor gap is that it doesn't explicitly state what is returned (e.g., user profile fields), but the output schema likely covers that.

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 and schema description coverage is 100%, so the description bears no burden for parameter documentation. A baseline of 4 is appropriate as the description adds no param-related information but none is needed.

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 clearly states 'Get current user profile', which is a specific verb and resource. It unambiguously identifies the tool's purpose and is distinct from sibling tools like pc_get_sidebar_preferences_me or pc_get_agents_me.

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 does not mention when not to use it, prerequisites, or context. For example, it doesn't clarify that this is the tool to use when needing the authenticated user's profile info, as opposed to pc_get_agents_me or other profile-related tools.

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