tutor_start

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

Annotations already indicate mutation (readOnlyHint=false, idempotentHint=false). The description adds the behavioral context of starting a session but does not disclose additional traits like session lifecycle, overwrite behavior, or resource requirements. Adequate but not enhanced beyond annotations.

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 two sentences, front-loading the core action. Every word is purposeful, with no redundancy. It effectively communicates the tool's function and key mode options in minimal space.

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 that an output schema exists and parameters are well-documented in the schema, the description covers the essential purpose and mode guidance. It could be slightly more complete by explaining how to choose between modes or error handling, but it is largely sufficient for an agent to understand 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 100%, so parameters are fully documented in the schema. The description's mode examples (socratic, avicenna) add minimal value beyond what the schema already states for each enum value. Baseline score is appropriate.

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 starts an L4 mentor/tutor session, using a specific verb and resource. It distinguishes between modes (socratic, avicenna) but does not differentiate from sibling tools like tutor_turn or tutor_record_mastery, leaving some ambiguity about when each should be used.

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 provides mode selection advice but no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, order of operations (e.g., call before tutor_turn), or scenarios to avoid. An agent lacks context for correct invocation.

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