share_lesson_sync_login_url

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

Annotations already flag openWorldHint=true and readOnlyHint=false, so the external-auth nature is partly covered. The description adds real workflow context the annotations cannot convey: the URL is lesson-sync specific, not general login, and the callback code feeds a subsequent sync-task creation. It omits whether a prior login is required, URL lifetime, and what a failure looks like.

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 compact sentences with the tool's distinguishing trait front-loaded. No filler, though the terseness is partly what leaves the parameter unexplained.

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?

An output schema exists, so return values need no prose. However, for an OAuth-style initiation step in a multi-tool flow (share_lesson_sync_start / share_lesson_sync_status), the description lacks auth prerequisites, the redirect_uri contract, and where the callback code is consumed, leaving the flow underspecified.

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 single optional parameter redirect_uri has 0% schema description coverage and is never mentioned in the description. The phrase '回调 code' hints at a redirect/callback flow but does not explain what value redirect_uri should take or what happens when it is omitted, leaving the agent to guess.

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 names a specific verb+resource: fetch the lesson-sync-dedicated jAccount authorization URL, and explicitly contrasts it with normal site login. This lets an agent distinguish it from the generic share_login_start flow. It stops short of naming the sibling tool outright.

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?

'与普通站点登录不同' implicitly tells the agent to use this for course sync rather than the regular login path, and the second sentence supplies the follow-up step (use the callback code to create the sync task). It gives clear context but never explicitly names the alternative tool or states preconditions such as requiring an existing session.

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