get-replay

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

With no annotations provided, the description carries full burden but only states the read operation without disclosing behavioral traits. It omits crucial details about the delivery modes (file vs resource), payload size limits, or what format the replay data takes.

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 single 9-word sentence is efficiently structured and front-loaded with the action verb. However, given the absence of annotations and output schema, the extreme brevity leaves critical behavioral context undocumented.

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 tool has 5 parameters with complex delivery options and no output schema or annotations. The description fails to compensate by explaining return values, payload structure, or behavioral differences between 'file' and 'resource' delivery modes, leaving significant gaps.

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?

Input schema has 100% description coverage, documenting all 5 parameters including the enum values for 'delivery'. The description implies required identifiers ('specific session replay') but adds no semantic meaning beyond what the schema already provides, warranting the baseline score.

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 states a clear verb ('Get'), target resource ('replay data'), and scope ('specific session replay in Rollbar'). It distinguishes from siblings like list-items or get-deployments by specifying 'replay' context, though it could clarify relationship to get-item-details.

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 context ('for a specific session replay') but provides no explicit when-to-use guidance, prerequisites for the identifiers, or comparison to sibling tools like get-item-details that might overlap in functionality.

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