wafle_users_me

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

Annotations already mark it read-only and idempotent. The description adds meaningful operational context: the session token requirement and the 401 failure mode for legacy API keys. It also reveals the return scope (profile, memberships, current tenant), which is extra value beyond annotations.

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?

Two sentences with front-loaded purpose. The first sentence states exactly what the tool returns; the second gives the critical auth requirement. No verbose or redundant content.

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 0-parameter, read-only identity endpoint, the description is complete: it covers purpose, return scope, authentication requirements, and failure conditions. The annotations are strong, and no output schema is needed given the described payload.

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, so the baseline is 4. The description adds no parameter-specific semantics because none are needed; the empty schema is already fully described.

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 'Return the currently-authenticated human's profile + memberships + current tenant' — a specific verb+resource scope. The 'human' qualifier differentiates it from system-level auth or membership-only tools, and the annotation title reinforces the 'who am I' purpose.

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?

It explicitly states the prerequisite: 'Requires a session token (WAFLE_USER_SESSION)' and gives a clear exclusion: 'Will fail with 401 if the MCP is using a legacy API key.' This tells the agent when the tool is appropriate, though it does not name alternative tools.

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