qui_get_automation_activity_run

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

The readOnlyHint annotation already indicates a safe read operation, and the description's use of GET aligns with that. It adds the argument structure convention but does not disclose potential errors, authentication needs, or return behavior. No contradiction with annotations.

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 description is a single sentence that front-loads the endpoint and then summarizes the argument convention. There is no filler, but it could be slightly clearer by stating the purpose before the invocation details.

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?

Given the generic input schema and presence of an output schema, the description provides the essential argument structure but lacks usage context, required parameter specifics, and comparison with siblings. It is adequate but not comprehensive for an agent to confidently select and invoke the tool.

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%, so the description partially compensates by explaining the argument layout (path variables, params, body) and naming {instanceID} and {activityId} in the URL. However, it does not enumerate all possible path/query/body parameters, leaving some ambiguity.

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 clearly states the endpoint being called (GET /instances/{instanceID}/automations/activity/{activityId}), which identifies the resource and operation. It distinguishes from siblings like list_automation_activity by targeting a single activity, though it does not explicitly state 'retrieve details'.

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?

No guidance is given on when to use this tool versus alternatives such as list_automation_activity or delete_automation_activity. It only explains how to structure arguments, not when this tool is the appropriate choice.

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