log_activity

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

With no annotations, the description carries the full burden. It discloses the side effect of auto-creating missing entities, which is a key behavioral trait. However, it does not mention other important aspects like idempotency, overwrite behavior, or required permissions.

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 extremely concise (three short sentences) and front-loaded with the core purpose. Every sentence adds unique value: the first states the primary function, the second reveals a side effect, and the third provides actionable examples.

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 the tool has 5 parameters and no annotations, the description is somewhat incomplete. It does not explain the role of most parameters or how they interact. The existence of an output schema mitigates the need to describe return values, but the description lacks depth for proper usage.

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?

Schema description coverage is 0%, and the description only adds context for the 'action' parameter by listing common values. The other four parameters (summary, entity_names, tags, metadata) receive no elaboration, leaving their semantics unclear despite the schema titles.

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's purpose with a specific verb-resource combination: 'Record what happened this turn.' It also lists common actions, which distinguishes it from sibling tools that focus on entity manipulation or memory queries.

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 through the list of common actions, but does not explicitly state when to use this tool versus alternatives like add_observations or create_entities. No guidance on when not to use it is provided.

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