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

The description discloses several behavioral traits beyond annotations: it runs four model turns server-side (read-back, schema check, step extraction, tracks and triggers), provides step→span table for provenance, requires a token, costs a model call per turn, and is capped per day. This is rich context that annotations do not provide, and no contradiction with readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false.

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 fairly concise, covering purpose, usage, behavior, and requirements in about five sentences. It front-loads the primary purpose and usage context early, then details the process and constraints. It is slightly dense but each sentence adds value. Not overly verbose, but could be slightly more succinct in unessential details like 'read-back' enumeration.

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 the tool's complexity (multi-step import with server calls, token requirement, cost and quota, output with step span), the description is nearly complete. It explains the output (program plus step→span table) despite lacking a formal output schema, and provides enough usage guidance. The only minor gap is not specifying the exact format of the step→span table or how errors are surfaced, but the description is sufficiently complete for an agent to decide to invoke it.

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?

While schema coverage is 100% and every parameter has a description, the tool description adds value by explaining how parameters are used in the import flow: for example, 'hints' is used as the scenario prompt's environment and resource constraints, 'environmentType' fills the scenario prompt's environment slot and becomes the program's environmentType. The description also explains that 'text' is read back in turn 1 and extracted in chunks. This goes beyond the schema descriptions.

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's purpose: converting pasted text into a validated multi-track programUTE. It uses specific verbs ('Turn', 'import') and a clear resource ('block of pasted text' converting to a 'Rhylthyme program'), and distinguishes itself from import_from_source by specifying that it is for pasted text with no URL or supported service. This differentiates it from siblings.

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 explicitly states when to use this tool: when the user pastes steps themselves and no structural importer fits (no URL, no supported service, a photo transcribed, PDF copied out). It also implies when not to use it (when a structural importer fits), providing clear context and alternatives. It also mentions external requirements (user's token from login) and cost implications.

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