plu_get_auth_user

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

With no annotations, the description must disclose behavior. It only states 'Get authenticated user info', which implies the tool requires authentication and returns user info, but it does not specify what happens if the user is not authenticated, what exact data is returned, or whether it has side effects. The description is too vague to fully understand the tool's behavior.

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 very concise with a single phrase, which is efficient for a simple tool. However, it could be slightly more informative without sacrificing brevity, such as listing a few key fields of the user info. Still, it is not overly verbose.

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 simplicity (no parameters, no output schema, no annotations), the description is expected to provide more context about the returned data or its relation to other tools. It fails to do so, leaving the agent uncertain about what 'authenticated user info' entails.

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 add parameter details, and the schema coverage is trivially 100%. No issues 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 clearly states the tool's action (Get) and resource (authenticated user info). However, it does not distinguish from the sibling tool 'plu_auth_status', which might serve a similar purpose, leaving ambiguity about when to use this tool over the other.

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?

No guidance is provided on when to use this tool versus alternatives like 'plu_auth_status'. There is no mention of prerequisites, context, or exclusions, making it difficult for an agent to decide whether this tool is appropriate.

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