self_distill_status

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

Annotations already declare readOnlyHint=true, and the description aligns with that by stating it shows status. The description adds valuable context about what components are reported, but lacks disclosure of potential prerequisites (e.g., requiring a prior run). Overall, it complements annotations well.

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?

Single sentence, concise, front-loaded with the action and key details. No unnecessary words.

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?

Given no input schema, no output schema, and a simple read-only operation, the description is mostly complete. It might lack details about when the tool is valid (e.g., if no self-distillation has been run), but for its purpose it is sufficient.

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?

There are no parameters, so the description carries the full burden of explaining what the tool does. It clearly communicates the output categories (sessions, lessons, signals), adding meaning beyond 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 clearly states the tool shows status of the last self-distillation run, specifying the outputs: sessions analyzed, lessons generated, signals detected. It is a specific verb-resource pair and distinguishes from the sibling tool run_self_distill.

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 implies usage for checking results after a self-distillation run but does not explicitly state when to use or when not to use, nor does it mention alternatives. Usage is implied but not directly guided.

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