Get Transaction Snapshots

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

Annotations already declare readOnlyHint and destructiveHint. The description adds significant behavioral context beyond those: snapshots are deep diagnostic captures showing call graphs, SQL, HTTP calls, and return an array with timing and error details. No contradictions exist.

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?

Description is short, front-loaded with purpose, and well-structured with an Args list. Every sentence adds value with no waste. Efficient use of space.

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 7 parameters and no output schema, the description covers purpose, snapshot content, and return type. However, it lacks guidance on how data collector filters interact or parameter relationships. Minor gap but mostly complete.

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 100%, so baseline is 3. The description repeats parameter info and adds default/max values (e.g., maxResults defaults to 20, max 100) already present in schema. No additional semantics beyond what 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?

The description explicitly states 'Retrieve transaction snapshots (slow, error, stall) for an application,' using a specific verb and resource. It clearly distinguishes from sibling tools by focusing on diagnostic captures rather than health rules, dashboards, or other entities.

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 explains what snapshots are but provides no guidance on when to use this tool versus alternatives like appd_get_errors or appd_get_health_violations. Usage context is implied through resource type, but no explicit when-to-use or when-not-to-use is given.

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