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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond the endpoint path plus a pointer to describe_operation - no disclosure of what 'activity' returns, pagination, or filtering behavior.

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?

The one meaningful sentence is duplicated verbatim, wasting the entire body of the description, and no information is front-loaded beyond the raw route.

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 no output schema and 0% schema coverage on both parameters, the description would need to explain the run-activity payload and query filters to be usable. It provides neither, delegating everything to describe_operation without telling the agent when that delegation is warranted.

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%, with an `id` path param and an untyped `query` object, so the description must compensate and does not. The ':id' in the path hints that id is the run identifier, but nothing explains accepted query parameters or constraints (maxLength 2000).

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 is essentially the endpoint path restated twice, so the resource (journal-close run activity for a given id) is inferable only by decoding the URL. It offers no verb-level description of what the 'activity' payload contains and does nothing to distinguish it from the many sibling journal-close runs endpoints.

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 only guidance is the pointer that 'describe_operation provides native request schemas', which vaguely indicates an alternative tool for schema lookup. There is no statement of when to call this vs. the numerous sibling run endpoints (batches, profiles, unassigned, workspaces) or what preconditions apply.

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