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

Beyond the readOnlyHint annotation, it discloses that it is read-only, that secrets in log lines are redacted, that results stay under 8 KB, and that unresolved parts mean a read did not happen rather than a finding. It also explains fallback resolution across Ankra Pipelines, the Ankra application, and OCI revision labels, which is rich behavioral context an agent needs.

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 long but front-loads its purpose in the first sentence and structures the five returned components as a numbered list, so it remains navigable. It is dense and could be trimmed if an output schema existed, but for a tool with no output schema the detail is largely earning 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?

With no output schema, the description carries the full burden of explaining return values and does so thoroughly: it enumerates the five result components, the resolution fallback chain, the grouping behavior, and the size and redaction constraints. An agent has enough information to call it correctly and interpret the result.

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 the schema already documents all six parameters including their defaults and enum. The description does not add per-parameter meaning beyond what the schema provides, so the baseline of 3 is appropriate for a tool whose parameter semantics are fully carried by 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 and resource — a single compact read that returns runtime context (image-to-commit mapping, revision timing, error log lines, stack frames, restart details) for a Kubernetes workload. It is unmistakably distinct from siblings like get_pod_logs or get_deployments because it aggregates commit provenance, logs, and stack frames together, and it frames itself as the first call for debugging code.

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?

It gives explicit when-to-use guidance: call it FIRST when fixing, debugging, or explaining a crashing service, when asked which commit a workload runs, or before handing a production error to a coding agent. It does not name alternative tools or state when not to use it, so it falls short of the top score, but the triggering conditions are clear and actionable.

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