tcai_self_model

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only names a state and its components. It does not state whether the tool is read-only, whether it has side effects, what it returns, or what errors may occur.

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 very short and front-loaded, but it is under-specified rather than efficiently concise. The colon-delimited list does convey some content, yet the lack of a verb makes it a fragment rather than a structured tool explanation.

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?

This is a state-related tool with no output schema, no annotations, and no action verb. The agent has no way to know what invoking this tool returns, when it is appropriate, or what behavior to expect, so the description is severely incomplete.

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 tool has 0 parameters and an empty input schema, so the baseline of 4 applies. The description does not need to explain parameter behavior because there are no parameters.

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 is a noun fragment ('Self-representation state: interoception, epistemic model, temporal continuity, attention schema') rather than an action. It mostly restates the tool name and lists subject areas, but does not state what operation the tool performs (e.g., get, update, log).

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 guidance on when to use this tool or how it differs from sibling tools such as tcai_metaconsciousness or tcai_workspace_state. No alternatives, exclusions, or contextual triggers are mentioned.

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