axint.session.start

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

Discloses that it writes files and does not require auth/network, aligning with readOnlyHint=false. Annotations are minimal but description adds meaningful context beyond them. No contradiction.

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?

Well-structured with separate action, effects, and usage sections. No unnecessary words, though slightly verbose for the content.

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?

Covers purpose, usage, effects, and constraints adequately. Output schema exists so return value details are not needed. Lacks mention of defaults for optional parameters, but schema provides them.

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 100%, so the description adds little beyond the schema. It mentions targetDir and projectName implicitly but does not provide additional semantics.

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 initiates an enforced Axint agent session and lists the written artifacts and return values. However, it does not explicitly differentiate from sibling tools like axint.context.memory, though the specific action is distinct.

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?

Explicitly states when to call ('start of a tool-enabled agent session or after context compaction') and includes a notable constraint ('no auth or network required'). Lacks explicit 'when not to use' or comparison to alternatives.

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