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

With no annotations, the description carries the full behavioral burden and does well: it states that the tool is mutating, that the first call for an id creates the workflow_executions row, that later calls append Activity timeline rows, and that actions land on the entity's Activity timeline. It does not describe permissions, error behavior, or rate limits, but the core side effects are disclosed.

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 front-loaded with the core action and then moves into identity and completion details. It is dense but generally earns its length given the 16-parameter schema, though it repeats enum values already present in the schema and could trim some of that duplication.

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, mutating tool with no annotations, no output schema, and 0% schema description coverage, the description supplies essential context about identity and lifecycle behavior. It remains incomplete regarding optional parameters, permissions, and return/error behavior, so an agent can invoke it but not fully understand all invocation scenarios.

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 must compensate. It explains key semantics for entityType, actionType, SMART_TEST identity via the nested test object, other entity identities via entityIdentity, and completion using WORKFLOW plus catalog workflow_id. It leaves many optional traceability parameters such as gitSha, userId, actorType, agentModel, branchName, cliVersion, policyFile, and skillVersion 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?

The description gives a specific verb and resource: 'Report a mutating agent action under a stable workflow-execution-id (ULID).' It also explains the create-vs-append behavior, which makes the tool's scope clear. However, it does not explicitly distinguish this tool from the many sibling reporting tools such as report-sast-findings or report-deps-findings.

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?

Usage is implied through 'Report a mutating agent action' and the note that the first call creates the row while later calls append timeline rows. The description does not state when to choose this tool over alternatives, nor does it give explicit exclusion conditions. The 'Do not use platform UUIDs' line is an identity constraint, not a usage guideline.

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