aidex_session

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

With no annotations provided, the description carries full burden and discloses key behaviors: it performs file change detection, auto-reindexing, and returns session history info. However, it doesn't mention potential side effects like performance impact during reindexing or error handling for invalid paths.

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 front-loaded with the core purpose, followed by bullet-like functions and a clear use case. Every sentence adds value: the first states what it does, the second lists specific actions, and the third explains when to use it. No wasted words.

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 annotations, no output schema, and one parameter, the description is mostly complete: it explains purpose, usage, and behaviors. However, it lacks details on return format (though hinted at with 'info') and doesn't cover edge cases like missing .aidex directories.

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% with one parameter documented as 'Path to project with .aidex directory'. The description doesn't add parameter details beyond the schema, but with high coverage and only one parameter, the baseline is 3. It earns a 4 by implicitly contextualizing the path parameter through the tool's purpose of session management.

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 verb 'Start or check' with the resource 'AiDex session' and lists three specific functions: detecting externally changed files, auto-reindexing modified files, and retrieving session metadata. It distinguishes from siblings by focusing on session initialization and history queries rather than file operations, indexing, or project management.

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 explicitly states when to use this tool: 'at the beginning of a new chat session' and for queries about 'What did we do last session?'. This provides clear context for usage versus alternatives like aidex_status for general status or aidex_query for specific searches.

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