get_iself_journal

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

Since no annotations are provided, the description carries the full disclosure burden. It explicitly states required scope ('iself:journal:read'), governance by Arbiter policy, and ProofLink receipt sealing, and describes the return content in detail. While it doesn't explicitly label the operation as read-only, the verb 'Retrieve' and the read scope imply safety; missing are error conditions or rate limits, but these are not essential for basic invocation.

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 main purpose is front-loaded in the first sentence, and the second paragraph succinctly list access and governance requirements. However, the claim 'has healed 11+ incidents' is arguably promotional rather than instructional, and the sentence about iSELF frequency could be considered extraneous; despite this, the overall length is appropriate and well-organized.

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 tool with one optional parameter and no output schema, the description is quite complete: it explains the return content, the scope requirement, and the governance/security context. It covers everything an agent likely needs to decide whether and how to call it. The only minor gaps are potential error handling or response specifics, but these are not critical given the schema already documents the parameter.

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 covers the sole 'limit' parameter with a full description (default 20, max 100), so the schema does the heavy lifting. The description adds nothing about parameter behavior beyond what the schema already states, matching the baseline expectation for high schema coverage.

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 opens with the specific verb 'Retrieve' and names the exact resource 'iSELF (Self-Healing Loop Framework) healing history', immediately distinguishing it from siblings like list_recent_incidents or get_platform_briefing. It further clarifies the content (service failure, diagnosis, patch, success, confidence), making the tool's function unmistakable.

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 context by explaining that iSELF runs every 5 minutes and what the journal covers, which implies when an agent would need this data. However, it does not explicitly state when not to use it or name alternatives (e.g., for general incidents), so it stops short of full exclusion guidance.

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