get_system_trace_status

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

No annotations are provided, so the description carries the full behavioral burden. It hints at mutation and ownership ('reconcile', 'owned trace', 'finalise') but does not disclose whether the call changes state, is idempotent, requires permissions, or what happens if the trace is not duration-completed.

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 definition is a single front-loaded sentence with no filler, but it is dense with unexplained jargon ('reconcile', 'finalise duration-completed capture'). It is concise without being clear.

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 annotations, no output schema, and a 0%-covered parameter, the description should explain side effects, return state, and completion behavior. It gestures at these ideas but does not provide enough detail for an agent to call the tool confidently.

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 the description adds no meaning about traceId beyond implying the trace must be 'owned'. It does not explain how to obtain the ID or what ownership entails, leaving the single parameter largely 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 names a verb ('reconcile', 'retrieve') and a resource ('trace'), but 'reconcile an owned trace' and 'finalise duration-completed capture' are ambiguous jargon. It does not clearly distinguish the tool from siblings like get_system_trace_capabilities, stop_system_trace, or cancel_system_trace.

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?

There is no explicit guidance on when to use this tool versus stop_system_trace, cancel_system_trace, or get_system_trace_capabilities. The phrase 'duration-completed capture' hints at a condition but does not state it as a usage rule.

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