get_log_slice

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

No annotations are present, so the description carries the behavioral disclosure burden. It honestly discloses that the tool is unavailable and that invoking it will provide the reason, which is a meaningful behavioral trait. However, it does not specify the exact response or error format, leaving some uncertainty.

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 one short sentence with no filler, and the key action is front-loaded. It is concise and readable, although this conciseness comes at the cost of substantive functional information.

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 zero-parameter stub with no output schema, the description tells the caller what happens when invoked and why it happens. Yet it does not explain the tool's original purpose or how it relates to sibling tools, leaving an agent unable to judge when the tool would be relevant beyond diagnostics.

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?

The schema contains zero parameters and has 100% schema coverage, so the description has no parameter-documentation burden. The baseline of 4 applies; the description's implication that the tool can be called without arguments is consistent with the empty 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 only states that the tool is unavailable and that calling it will reveal why; it never says what get_log_slice is meant to do, such as retrieving a slice of logs. It reads as a status note rather than a tool-purpose statement and offers no differentiation from sibling run/check tools.

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 only usage guidance is the imperative to call the tool to see why it is unavailable. There is no explanation of when this tool should be used relative to the listed siblings, and no alternative tools or exclusion conditions are given.

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