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

Annotations already declare the write/idempotency/safety profile, but the description adds material context beyond them: a sign-in requirement with the exact bootstrap calls, and tenancy scoping ("It stays inside this trial_id"). It does not clarify the upsert-vs-create behavior implied by "save or update" against idempotentHint=false, which is the only remaining gap.

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?

Three sentences, front-loaded with the blocking prerequisite, then purpose, then the sibling boundary — every sentence earns its place. The first sentence is densely packed with two calls and a parenthetical, but nothing is wasted.

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 six-parameter mutation tool with 100% schema coverage, no output schema, and annotations covering the safety profile, the description supplies the missing pieces an agent needs: auth prerequisites and the save-vs-publish boundary. Only the create-vs-update result semantics remain unaddressed.

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 100%, so all six parameters (body, title, session, summary, trial_id, workflow_id) are already documented in the schema. The description only touches trial_id implicitly ("stays inside this trial_id") and adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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 pair ("Save or update") and resource ("one private compliance playbook") with scope ("for this keyless trial"). It explicitly distinguishes the action from the sibling publish_workflow, so an agent can route between them without opening either schema.

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?

Gives an explicit prerequisite sequence (call connect(email) and connect_verify first, unless already signed in) and an explicit alternative ("call publish_workflow only to mark it ready here, never to share it with another user"). The when-to-use condition is stated, not implied.

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