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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is added context, and it delivers by enumerating exactly which data categories are retrieved — the closest thing to output disclosure since there is no output schema. It stops short of noting edge cases (missing breadcrumbs, unknown errorId behavior), which keeps it off a 5.

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?

One front-loaded sentence that leads with the outcome ("everything recorded around an error") and then itemizes the payload. No filler; the only near-redundant item is the vague trailing "extra data".

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 must describe the return, and it does so at category level, which is sufficient for a single-parameter read tool. Missing only minor operational details: what happens when the errorId is unknown or when fields are absent.

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?

Only one parameter, and the schema documents it at 100% coverage ("The error ID to get context for"). The description adds nothing about id format or source (where to obtain a valid errorId, e.g. from search results), so the baseline 3 applies.

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 uses a specific verb ("Returns") plus a precisely enumerated payload: breadcrumbs, platform, runtime, OS, environment, release, user, agent session, extra data. That enumeration implicitly separates it from runheed_get_error (the error record) and runheed_search_errors, but no sibling is named explicitly.

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?

Usage is only implied by the word "context" — an agent can infer this is the detail-expansion call after runheed_get_error or runheed_search_errors, but the description never says so. There are no when-not conditions, no mention of prerequisites, and no routing to the sibling that returns the error itself.

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