tcai_self_model

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

No annotations are provided, and the description fails to disclose any behavioral traits such as read-only vs mutating, side effects, or performance implications. The abstract list of concepts gives no insight into tool behavior.

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 concise (one short phrase), but it lacks a verb or action word that would front-load the purpose. Brevity at the expense of clarity prevents a higher score.

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 tool with no parameters and no output schema, the description should clarify what the tool returns or accomplishes. It merely lists abstract concepts without explaining how the agent should interact with this state.

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 schema coverage is effectively 100%. The description does not need to add parameter semantics, but it also does not compensate by explaining the output or behavior, which would be expected given 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?

Description lists components of the self-model (interoception, epistemic model, etc.) but lacks a verb to indicate what action the tool performs. It reads as a label rather than a functional description, making it unclear whether this tool retrieves, updates, or processes the self-representation state.

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?

No guidance on when to use this tool compared to siblings like tcai_metaconsciousness or tcai_workspace_state. It does not specify prerequisites or context, leaving the agent to guess.

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