add_setup

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

Annotations indicate this is a write operation (readOnlyHint=false). The description adds behavioral context: it registers a setup, tracks overdue via 'payoff_by', and mentions the ledger metaphor. However, it doesn't explicitly state that a record is created or describe the return value, but the core behavior is clear.

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 concise, front-loaded with the main purpose, and every sentence adds value. It uses a clear structure with parameter explanations embedded, no wasted words.

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?

Given the 5 parameters and no output schema, the description covers the main usage well. It explains the purpose of each parameter and the overdue tracking. However, it does not describe the return value or success indication, which would be helpful. But overall it's fairly complete for a register tool.

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 0%, but the description fully explains each parameter: 'setup' as the description of the setup, 'chapter' as where it is told, 'payoff_by' as optional deadline chapter with overdue display, and 'thread' as identifier. This adds significant meaning beyond the bare schema.

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 clearly states the verb 'register' ('登録する') and the resource 'foreshadowing/Chekhov's gun' ('伏線(チェーホフの銃)'), along with the purpose of tracking uncollected ones ('未回収を追跡する'). It distinguishes itself from the sibling tool 'resolve_setup' which closes setups.

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 provides explicit when-to-use guidance: register a setup. It mentions the alternative: close with 'resolve_setup' when collected. It also explains the meaning of parameters and how 'payoff_by' triggers overdue display in 'chapter_brief/open_setups', giving clear context.

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