capture_form_baseline

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

The description says the tool creates and saves a baseline snapshot, i.e. it persists new state, while annotations declare readOnlyHint=true. That is a direct conflict about whether the call mutates anything. The disclosure that provenance/publication are not verified is genuinely useful context, but it does not resolve the read/write contradiction.

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 load-bearing: the first defines the action and the hash output, the second front-loads the critical non-verification caveat. No filler or 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 tool that persists a snapshot from a caller-supplied nested object, with no output schema and an undescribed payload structure, the description omits where the baseline is stored, what identifier or hash is returned, and whether repeated captures overwrite prior baselines. It also leaves the read/write nature ambiguous against the annotation.

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 33%: environment_profile is documented in the schema, while 'form' is an untyped object and 'label' has only a maxLength. The description adds 'caller-supplied' for the form payload but says nothing about the expected form shape or what 'label' means, leaving two of three parameters semantically opaque.

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?

States a specific verb and resource: create a 'caller-supplied saved form baseline snapshot with an integrity hash'. The qualifier 'caller-supplied' implicitly separates it from capture_published_form_baseline, and 'does not verify provenance or publication' separates it from verify_form_baseline. It never names those siblings explicitly, so a 4 rather than a 5.

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 exclusion ('does not verify provenance or publication') hints that this is the right call when you already have a form payload and don't need validation, and that verify_form_baseline covers the checking case. But there is no explicit when-to-use statement, no prerequisites, and no named alternative, so selection depends on inference from the sibling list.

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