workflow_import_pod_roster

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

With no annotations, the description carries the full burden and does disclose one meaningful trait: persistence must follow explicit human confirmation. But it is silent on the behavior implied by 'persist' beyond that — overwrite semantics, expectedRevision conflict handling, and reversibility are undisclosed.

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?

A single front-loaded sentence with zero filler. The action and its gating condition are both stated within one line, with no redundant restatement of the title.

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 complex mutation with 4 undocumented required params, no annotations, and no output schema, a one-line description leaves major gaps — notably how expectedRevision guards against stale writes. It is incomplete relative to the tool's surface complexity.

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 all 4 parameters are required, so the description must compensate. It only loosely gestures at 'roster' (mapping to memberships) and never explains journeyId, expectedRevision, or the const-true confirmed flag. Most parameter intent remains undocumented.

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+resource ('Persist a ... Pod roster') and implies a precondition ('validated'). The qualifier 'validated' hints at the sibling workflow_validate_pod_roster but never names it, so sibling differentiation is only implicit. Clear enough for an agent to grasp the action.

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?

'only after explicit human confirmation' is a genuine usage precondition, which is more than most definitions offer. However, it does not name the validate step as an alternative/prerequisite tool or state when this should not be called, leaving routing to inference.

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