Register Foreshadow

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

With no annotations, the description fully carries the burden of behavioral disclosure. However, the Chinese phrase only restates the tool name and discloses nothing about side effects, required permissions, or what 'registering' entails.

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 is extremely short but under-specified rather than concise. It provides no informative content beyond the title, making it a tautology that wastes the opportunity to add 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 an 8-parameter tool with no output schema and no annotations, a one-word description is completely inadequate. Agents cannot understand field dependencies, required fields beyond the schema, or return behavior.

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?

Schema description coverage is only 38%, leaving many parameters undocumented. The description adds no parameter explanations, so agents must guess semantics from English property names alone (e.g., 'planted_at' as a scene location).

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 '登记伏笔' translates directly to 'Register Foreshadow', which restates the title. It does not provide a specific verb+resource description and fails to distinguish the tool from siblings like 'get_open_foreshadows' or 'pay_off_foreshadow'.

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?

No guidance is given on when to use this tool versus alternatives. The sibling list includes other foreshadow-related tools, but the description offers no context or selection criteria.

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