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

With no annotations, the description carries the full disclosure burden. It does convey that the operation is authenticated/scoped to the project and that the result is a batchViewUrl intended to be relayed to a user, which implies a read-only lookup. It does not state behavior when the ID is unknown or invalid, nor whether results are cached or live.

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 short sentences, front-loaded with the action and scope, then the input and the return field. Nothing is padded, though the '--' flag phrasing is a minor stylistic slip.

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 tool with no output schema, the description covers the action, the input name, and the returned field, which is most of what an agent needs. It omits error/failure behavior and any prerequisite for obtaining a valid batch invocation ID.

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 there is one required parameter, so the description must supply meaning. It only restates the parameter name in CLI-flag form ('Pass --batch-invocation-id'), adding no detail about what a batch invocation ID is, its format, or where to obtain it, and the flag notation is slightly at odds with an MCP object parameter.

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 (resolve) and resource (TestChimp batch execution viewer deeplink) scoped to the authenticated project, which is far more informative than a name restatement. It does not explicitly distinguish itself from near-neighbors like fetch-execution-report or get-last-run-workflow-detail, leaving some selection ambiguity.

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 phrase 'for messaging back to the user' implies the use case (produce a shareable link), which is a useful contextual hint. However, no alternative tool is named and no when-not-to-use condition is given, so the agent must infer that report-fetching siblings return data rather than a viewer URL.

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