get_myself

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

With no annotations provided, the description carries the behavioral disclosure burden. The verb '조회합니다' (retrieves) signals a read-only operation, and '현재 인증된 사용자' indicates the authentication context. It could describe return shape or error behavior, but for a simple self-info endpoint these are minor gaps.

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 consists of two short, purposeful sentences. The main function is front-loaded, and the second sentence adds practical guidance without padding or redundancy.

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 tool with no output schema, the description tells the agent what the tool returns (current authenticated user info) and why it might be used (account ID verification). It does not enumerate exact response fields, but that is a minor omission given the tool's low complexity.

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 rubric baseline is 4. Schema description coverage is trivially 100%. The description adds no parameter details, and none are needed because there is 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 states a specific verb and resource: it retrieves the current authenticated user's information. It clearly distinguishes this tool from siblings like get_issue, create_issue, and list_projects by focusing on the user identity rather than Jira/Confluence content. The account-ID use case further clarifies its 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?

The description explicitly says the tool is useful for checking the account ID, giving a clear usage context. It does not mention alternatives or exclusions, but no sibling tool serves this same purpose, so explicit exclusions are unnecessary.

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