trace_function

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

The description discloses the capture preset (args, return, stack) and that it hooks a function, but lacks details on side effects, persistence, or how the tracing data is returned. Given no annotations, this provides moderate transparency but leaves gaps.

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 very concise with two short sentences, front-loaded with the primary purpose. No wasted words; every part adds value.

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 tool has 3 parameters, no output schema, and no annotations, the description is incomplete. It does not explain parameters, return value, or side effects such as whether the hook is temporary or needs removal. Only the capture preset is mentioned.

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?

With 0% schema description coverage, the description fails to explain the three parameters (name, targetExpr, target). It only mentions 'Trace a function' and 'hook with capture preset', which does not clarify parameter roles or semantics beyond the schema property names.

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 'Trace a function' with a specific verb and resource, and mentions 'hook with capture preset [args, return, stack]' providing the scope. It distinguishes itself as a convenience wrapper for call-chain debugging from siblings like hook_function.

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 description implies usage for simple call-chain debugging via 'Convenience wrapper', but does not explicitly state when to use this tool versus alternatives like hook_function, nor does it provide when-not-to-use or exclusions.

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