Get Debug Log Body

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

Annotations already declare read-only and idempotent behavior. The description adds valuable context about the 24-hour retention limit and that it returns 'full text content.' This supplements the annotations without contradicting them.

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 concise sentences, front-loaded with the purpose. No filler or redundant content. Every sentence earns its place.

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?

For a simple one-parameter read tool with rich annotations and no output schema, the description adequately covers purpose, prerequisite, and a key limitation (24-hour retention). It doesn't specify error behavior, but that's not essential for this level of complexity.

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%, with the logId parameter already described as an ApexLog record ID with 15-18 characters and retention info. The description adds 'Get the logId from sf_get_debug_logs first,' which reinforces provenance but doesn't introduce new semantics beyond the schema.

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 specific verb+resource: 'Retrieves the full text content of a single Apex debug log by ID.' This clearly distinguishes it from sibling tools like sf_get_debug_logs (which lists logs) by emphasizing 'single' and 'by ID.'

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 clear usage context by instructing to 'Get the logId from sf_get_debug_logs first,' which indicates the prerequisite step. It doesn't explicitly mention when not to use it, but for a straightforward retrieval tool, the context is sufficient.

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