pin_set_trace

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 does not disclose that this mutates process state, whether it requires the target to be paused, whether changes take effect immediately or on next launch, or what happens to previously set flags. The flag constants are useful but they are parameter data, not behavioral disclosure.

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?

Two short sentences, front-loaded with the action, followed by the combinability rule. No filler, no repetition.

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?

The single required parameter is fully specified, so the core call is answerable. However, with no annotations and no output schema, and with siblings covering launch/pause/resume/read, the description should say more about when this is valid and what effect it has — that gap leaves the agent to infer operational context.

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 coverage is 100% and the schema already gives the 0x12 example, but the description adds the named constants (TF_TRACE_INSN=2, TF_REGISTERS=0x10, TF_TRACE_EVERYTHING=0x40) and the OR-combination rule that the schema does not encode since there are no enums. This meaningfully extends what the schema provides.

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 ('Set') and resource ('tracing flags'), and enumerates the concrete flag constants, so the agent can tell it apart from siblings like pin_trace_count or pin_status. It lacks any explicit sibling differentiation, but the purpose itself is unambiguous.

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 usage hint is 'Combine with bitwise OR', which is a syntactic note rather than a when-to-use rule. It never says whether flags must be set before launch, while paused, or which of the pin_* siblings to prefer for inspecting trace results.

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