manage_fair_evidence_bundle

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

No annotations are provided, so the description carries the full burden. It discloses only that the feature is enterprise-gated; it says nothing about whether bundling mutates state, where bundle_path is written, whether an existing bundle is overwritten, or what the required action values do. The middle sentence describes what a different (paid) product *would* do rather than what this tool does.

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?

Only the first sentence earns its place; the remaining two sentences are an upsell pitch and a pricing URL that give the agent no operational information. The useful scope statement is front-loaded, but roughly two-thirds of the text is marketing.

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?

With no annotations, no output schema, a required un-enumerated `action` parameter, and near-empty parameter documentation, the description must carry the definition — and it does not. An agent cannot reliably invoke this tool without guessing valid `action` values.

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 required `action` parameter has no description and no enum, and the description supplies nothing to compensate — this is the single most important piece of missing information. The other two parameters (`bundle_path`, `evidence_case_id`) are described in the schema only as "Default: ''", so the description adds no semantics anywhere.

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 first line names a resource ("Portable FAIR evidence bundles for air-gapped team transfer"), but the verb "manage" is never unpacked — the tool takes a required `action` parameter whose possible values are never revealed, so an agent cannot tell what operations are actually performed. Sibling FAIR tools (manage_fair_registry, manage_fair_characteristics, prepopulate_fair_draft) are not differentiated at all.

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 only conditional guidance is "Requires Kiln Enterprise," which is a licensing gate, not a when-to-use rule. There is no indication of which situations call for this tool versus the many other FAIR-related siblings, and no statement of prerequisites for the air-gapped transfer scenario.

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