complete_session

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

Discloses parallel execution of rollcall and attendance marking, but lacks details on error handling, rollback behavior, or permissions. No annotations provided to offset gaps.

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?

Two sentences, front-loaded with main purpose. No wasted words; efficient and clear.

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?

Adequate for a straightforward write operation with 6 required params and no output schema. Could mention return value or success indication, but not required.

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?

100% schema coverage with descriptions for all parameters. Description adds no extra meaning beyond schema; baseline score of 3 applies.

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 specifies verb 'Mark an ILT session complete' and resource 'ILT session', with clear action 'record attendance'. Distinguishes from sibling tools like 'register_user_to_session' and 'reset_session_score'.

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?

Implied usage for completing sessions and recording attendance, but no explicit guidance on when to use vs alternatives like 'update_module_progress' or 'bulk_register_users_to_session'.

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