twining_why

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

With no annotations provided, the description fully carries the burden of disclosing behavior. It explains that results are ranked by relevance, bounded by a token budget, and overflow decisions appear as one-liners with instructions to pass ids back for full detail. This is thorough and transparent.

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 very concise, using three short sentences to convey purpose, behavior, and usage. It is front-loaded with the most important information and contains no unnecessary 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 complexity (4 parameters) and no output schema, the description sufficiently covers the tool's behavior, parameters, and usage context. It explains the relevance ranking, token budget, and overflow mechanism, but could be slightly more detailed about the return format for full detail requests.

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 coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema, especially for the 'ids' parameter, explaining how to use it for full detail of overflow decisions. This provides useful additional guidance.

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 tool's purpose: 'Before modifying a file, check what decisions constrain it. Shows rationale and alternatives so you don't contradict prior choices.' It distinguishes itself from sibling tools by focusing on pre-modification decision checking.

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 clear context for when to use the tool ('before modifying a file') and describes the overflow handling mechanism, but does not explicitly exclude scenarios or compare to alternatives.

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