ddflow_session

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

No annotations are provided, so the description carries the full burden. It indicates a session log and lists actions, but does not disclose whether start creates a session, whether end closes or deletes it, whether calls persist, what permissions are needed, or what the tool returns.

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-loads the resource and action pattern. It is efficient, though the fragmentary phrasing ('Set `action`; required arguments in brackets') is somewhat cryptic.

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 an 8-parameter multiplexed tool with four actions, no annotations, and no output schema, so the description needs to do more. It covers only the action list and a partial argument mapping, leaving most parameters and the semantics of each action unexplained.

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 coverage is 100%, so the schema already documents all parameters. The description does add an action-to-argument mapping, but it labels `session` as required for `end` even though the schema says session is optional and can be omitted for the latest open. It also omits any explanation of item, tool, model, summary, and as_agent.

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 calls this 'The session log' and lists the action names note/end/prompt/start, which implies session lifecycle logging. However, it never states a clear verb or explains what each action actually does, so the purpose is only partially clear from the action names.

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?

It says to set `action` and gives bracketed arguments per action, but does not explain when to use this tool versus siblings such as ddflow_heartbeat or ddflow_brief. There is no when-to-use or when-not-to-use guidance beyond the action names themselves.

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