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

No annotations are provided, so the description carries the behavioral burden. 'Introspection' and 'inspect' reasonably imply a read-only operation, and the listed inspection areas add context. However, the description does not explicitly state that the tool has no side effects, what it returns, or any constraints, leaving room for inference.

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 a single front-loaded sentence with a clear colon-separated structure. Every word contributes meaning, and there is no filler or repetition.

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 introspection tool with an output schema, the description covers the essential substance and has no missing invocation requirements. It would be slightly stronger if it explicitly noted read-only behavior, but nothing needed to call the tool correctly is 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?

The schema has zero parameters, so there are no parameter semantics to document. The description still adds value by naming the areas inspected, which helps an agent interpret the tool's scope and potential output.

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 ('inspect') and identifies the resource ('self-model'), enumerating capabilities, domain competence, active subsystems, and safety status. It is clear, but it does not explicitly differentiate from overlapping siblings such as cognitive.assess_competence or cognitive.monitor_reasoning.

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?

There is no explicit guidance on when to use this tool versus alternatives. The only usage signal is 'introspection', which essentially restates the tool's function, and no exclusions or sibling comparisons are provided.

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