auth_me

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

No annotations are provided, so the description carries the burden. It discloses the return contents (user, organization, memberships, subscription) but doesn't state whether this requires authentication, what happens if unauthenticated, or whether this is a pure read with no side effects. The read-only nature is implied but not explicit.

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, concise and front-loaded. The first sentence states the primary purpose; the second clarifies the return structure. No wasted words, though the 'flat JSON' note adds mild 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?

For a zero-parameter simple read tool, the description is reasonably complete. It names all return sections (user, organization, memberships, subscription). No output schema exists, so listing return fields is appropriate. Could be slightly richer about auth requirements but adequate for a simple profile-fetch tool.

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 0 parameters with 100% schema coverage (empty properties object), so there are no parameters to document. Per the rubric, 0 params baselines at 4. The description effectively conveys there's nothing to configure.

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 it retrieves the current authenticated user profile, naming the specific resources (user, organization, memberships, subscription). It distinguishes from related auth_* siblings like auth_login/auth_register by explicitly being about the current authenticated profile, though it doesn't explicitly name any sibling alternative.

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 tool name 'auth_me' plus description implies usage when the agent needs current-user identity/session context. It distinguishes from auth_login/auth_register/auth_refresh by focusing on reading the current profile, providing clear context without explicit exclusions or alternative tool names.

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