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

Beyond the annotations, the description discloses two meaningful behavioral traits: the rule is budget-capped per run and overall, and nothing executes until the rule is approved. It does not explain whether preparation is idempotent, what draft state results, permission requirements, or how request_id affects retries, which leaves gaps for a mutation-style tool.

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 sentences, both front-loaded and free of filler. The trigger and spending-limit scope come first, followed by the approval gate, so every sentence adds useful information without repetition.

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 a 13-parameter, nested-object mutation with 0% schema description coverage and no output schema, the description is materially incomplete. It covers purpose, trigger, and budget/approval, but leaves required identifiers, bindings, conditions, and validity window unexplained, so an agent cannot confidently construct a call from the description alone.

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% and there are 13 parameters, so the description must carry parameter meaning. It explains the trigger behavior and spending-limit parameters but leaves most required inputs undocumented, including request_id, name, collection_id, function_id, bindings, valid_until, batch_size, conditions, reuse_completed, and include_existing.

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 a specific verb and resource: it prepares a research rule that runs on first-ready or input-change triggers, with spending limits. It also distinguishes itself implicitly from approval siblings via "Nothing runs until the rule is approved," though it does not explicitly name alternatives like approve_research_rule or patch_research_rule.

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?

It gives implied usage context by describing when the rule fires (first become ready or inputs change) and that spending limits apply. However, it offers no explicit when-to-use versus when-not-to-use guidance and does not name sibling tools such as prepare_investigation_batch or patch_research_rule.

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