wetrack_get_current_user

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

With no annotations provided, the description carries the burden of explaining behavior. It clearly indicates the tool returns the current user's profile and sidebar permissionsestrategically implies a read-only operation via 'Get', but it does not explicitly state authentication failure behavior or confirm the absence of side effects. The output schema covers return details, so this is adequate but not comprehensive.

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 two concise sentences with no filler. It front-loads the core action and resource, then adds a practical use case. Every sentence contributes value.

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 zero-parameter input, the presence of an output schema, and the simplicity of the read operation, the description is largely complete. It tells an agent what the tool returns and why it might be used. It could mention authentication prerequisites explicitly, but the phrase 'currently authenticated user' already implies them.

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)Skip, so the description cannot add much beyond the schema. The 100% schema coverage and absence of parameters make this baseline-4 appropriate; there is no parameter meaning left to clarify.

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 specific verb ('Get'), a precise resource ('currently authenticated user's profile and sidebar permissions'), and is clearly distinguishable from sibling tools like wetrack_get_user or wetrack_list_users. It directly conveys the tool's unique scope without ambiguity.

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 explicitly identifies a clear use case: verifying who is logged in and their role. It does not reference alternative tools or exclusions, but the intended context is readily apparent from the wording.

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