capture_published_form_baseline

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

readOnlyHint=true already tells the agent the target environment is not mutated, and the description usefully adds that no platform signature or lock is attached to the resulting artifact, which is a real trust caveat an agent should know. However, it never says where the baseline is stored, what 'organization evidence' consists of, or whether the artifact can be reused across environments, so the behavioral picture remains partial despite the helpful caveat.

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 tight sentences with the action front-loaded and the caveat trailing, which is the right ordering. Nothing is padded, though the second sentence reads as a fragment whose significance is not connected back to the first.

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 five parameters, four required, low schema coverage, and no output schema, the description needs to explain what the call produces and how the inputs map to it; it does neither. An agent can guess the general intent but cannot confidently supply form_id/logical_name/label or predict the returned baseline handle.

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 only 20% — just environment_profile is documented — so the description carries most of the burden and does not deliver. 'A named environment' is ambiguous between the required 'profile' and the optional 'environment_profile', and form_id, logical_name, and label receive no explanation whatsoever (is label a human-readable baseline name? a form display name?).

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 names a specific verb pair (read the published main form, create a portable baseline) and a specific resource, and the word 'published' implicitly separates it from the sibling capture_form_baseline, which presumably works on unpublished/draft forms. It stops short of explicitly naming that sibling or defining what a 'portable baseline' actually is, so an agent gets the gist but not the full distinction.

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?

There is no when-to-use guidance at all: nothing says when to capture a baseline versus calling verify_form_baseline, compare_environment_forms, or capture_form_baseline. The only contextual hint is 'from a named environment', which implies a per-environment snapshot workflow but never states prerequisites, ordering, or exclusions.

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