get_medal_summary

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

With no annotations provided, the description carries the full burden and says nothing beyond a gloss of the name. It does not state that the call is read-only, whether login is required, whether data is per-account or platform-wide, or what shape the response takes.

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?

A single short phrase with zero waste and no burying of key information. Its brevity reflects terseness rather than padding, though the phrase is too thin to be fully informative.

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?

A zero-param, annotation-free tool with no output schema depends entirely on the description to explain what a \"medal summary\" contains and what the platform-activity-completion figure represents. The description leaves both unanswered, so an agent cannot predict the result.

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?

Zero parameters, so there is nothing to disambiguate; the baseline applies.

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?

"任务勋章概览（平台活动完成度）" names a resource (medals) and a scope (platform activity completion), but the verb is only implied by the "get_" prefix and the term "概览" leaves the actual content ambiguous. No sibling tool overlaps, so differentiation is not an issue, but the purpose remains vague.

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 gives no indication of when an agent should call this tool versus its many siblings (account info, author overview, check-in tickets), nor any prerequisites such as being logged in. The agent must infer the trigger condition entirely.

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