heap_query_delta

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

No annotations are provided, so the description must convey behavioral traits. It implies a read-only query operation with no side effects, but does not explicitly state safety, authentication needs, or return format details. The mention of 'heaplog 风格文本' gives some indication of output style.

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 moderately concise but mixes languages and includes a separate 'Args' section. The examples add clutter. A more streamlined format with front-loaded key information would improve usability.

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 complexity (9 params, no schema descriptions, no annotations), the description covers all necessary aspects for a query tool: purpose, example usage, parameter explanations, and return type. The presence of an output schema reduces the need for detailed return format documentation.

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 adds value by explaining all 9 parameters. Each parameter has a brief but clear explanation, including filter semantics (e.g., caller_contains as substring filter, around_addr as center address). This compensates well for the schema's lack of descriptions.

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 it queries a specific file (/tmp/heap_delta.json) generated by heap-end, and allows filtering by caller and address. While it does not explicitly differentiate from siblings like heap_query_log, the specific resource and filtering capabilities set it apart. The examples further clarify its purpose.

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 provides example usage patterns (e.g., caller_contains='SLPParseSrvUrl', around_addr with size) that indicate when this tool is appropriate. However, it lacks explicit guidance on when not to use it or alternatives to consider. The sibling heap_query_log exists but is not mentioned.

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