Finish Wiki upload session

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

Annotations already declare the safety profile (readOnly=false, idempotent=false, destructive=false), so the bar is lower; the description still adds real behavior: the session must be finished before attachment, and the call returns the session with its final status. It omits what happens if invoked twice or on a session with no parts, which the non-idempotent hint makes relevant.

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, front-loaded with the action and its pipeline position, then the downstream constraint. No filler.

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 single-parameter session-lifecycle tool with no output schema, the description covers purpose, sequencing, and return value. Minor gaps remain around failure/idempotency behavior, but nothing essential to correct invocation is missing.

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?

Only one parameter (session_id) and schema description coverage is 100%, so the schema fully documents it; the description adds no format or semantic detail beyond the baseline.

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?

Specific verb+resource ('close an upload session') with explicit placement in the pipeline ('step 3 of the upload pipeline'), which cleanly separates it from the sibling upload_part (step 2) and abort tools.

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 a clear precondition ('after its last part') and a downstream routing cue ('only a finished session can be attached to a page'), naming attachments_attach. It stops short of stating when NOT to use it, e.g. that an incomplete session should be handled with wiki_uploadsessions_abort instead.

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