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

With no annotations, the description carries the transparency burden. It discloses key behavioral aspects: the request enters a content-demand queue, is reviewed daily, and optionally triggers an email notification. It doesn't describe the response format or failure modes, but for a simple submission tool, the disclosed behavior is sufficient and adds context beyond the operation name.

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 three sentences with the purpose first, followed by usage context and optional behavior. Every sentence earns its place; there is no redundant or vague wording. It is tightly structured and scannable.

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?

The description explains the request lifecycle (queue and daily review) and the optional notification, which covers the core context. The input schema documents all parameters, so no return-value explanation is needed since there is no output schema. It is complete enough for an agent to correctly invoke the tool without ambiguity, though the response/confirmation behavior is not mentioned.

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 coverage is 100%, so the parameters are fully documented individually. The description aligns with the schema by mentioning the optional email notification, but it doesn't add new meaning beyond what the schema already provides. The baseline of 3 is appropriate; the description doesn't compensate further for parameter-specific 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 verb ('Submit') and resource ('a request for a tutorial we don't yet have'). It explicitly distinguishes itself from sibling tools by specifying the trigger condition (search_tutorials returned no good match), making its purpose unambiguous.

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 explicit when-to-use guidance: 'Call this when search_tutorials returned no good match for what the user actually wants.' It also explains the downstream process (content-demand queue, daily review), which helps the agent understand the tool's role in the overall workflow, though it doesn't list explicit 'when not to use' scenarios beyond the condition.

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