get_role_manual

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

No annotations exist, so description carries full burden. Discloses return format {ok, role, manual} and error case {ok:False, hint}. Since it's a read-only retrieval, no major behavioral traits missing.

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?

Description is detailed but well-structured with bullet points and sections. Every sentence adds value; could be slightly trimmed but overall efficient for the information density.

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 one optional parameter and existence of output schema, description fully covers tool behavior, input meaning, output format, and error handling. No gaps.

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?

Input schema has one param 'role' with default but no description. Description fully compensates by explaining each possible value ('data','ingest','lecture','prep','variant','all') and their corresponding manual content, providing complete semantic coverage.

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?

Clearly states it retrieves the full role manual, distinguishes from sibling tools like get_feedback_sheet, and specifies each role's content. Mentions alternative MCP resource for specificity.

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?

Provides explicit guidance on when to use, e.g., first-time agents should call with corresponding role; suggests role='all' for fresh agents. No explicit when-not, but context suffices. Also references a resource alternative.

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