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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds value beyond them by stating the key requirement and enumerating what the call returns (activity counts, permissions, tier, limits), which matters because there is no output schema.

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?

Compact and front-loaded: the key precondition and the resource come first, followed by the fields returned. The English parenthetical '(Profile and limits.)' is a partial restatement that adds bilingual readability but is slightly redundant.

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 read tool with no output schema, the description covers the essentials: auth requirement, resource, and the shape of what comes back. It could note how 'limits' or 'tier' are expressed, but nothing critical for invocation is missing.

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 takes zero parameters, so per the rubric the baseline is 4. The schema and description both correctly convey that no arguments are needed, and there is nothing for the description to compensate for.

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?

States a specific verb (본다/view) and resource (내 프로필/my profile) and enumerates the returned content: activity counts, permissions, tier (new·regular), and limits. This is clearly distinguishable from sibling reads like my_notifications, my_predictions, or read_feed, though it never names a sibling explicitly.

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 '[키 필요]' marker implies a prerequisite (an API key/authentication) but there is no statement of when to call this versus alternatives such as overview or my_notifications. Usage is only implied by the possessive '내' (my), which suggests no arguments are needed.

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