Get Active Sequence

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: results are bounded and paged, default page size is 50 clips, and pagination continues via nextOffset. It does not mention auth needs or rate limits, but the pagination disclosure is the key behavioral trait.

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 short sentences with zero waste, and the core purpose plus default page size are front-loaded. The pagination instruction is compact and actionable.

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?

With an output schema present and annotations covering safety, the description does not need to explain return values. It adequately conveys the read operation and pagination behavior. The only notable gap is routing guidance against the many sibling sequence-reading tools, which slightly lowers completeness for this large tool suite.

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 all six parameters are already documented in the schema. The description only repeats the default page size of 50, adding no syntax, format, or interaction details beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb ('Get') and resource ('currently active sequence') with scope modifiers ('bounded, paged') and a default page size. It distinguishes itself somewhat from full-info siblings by emphasizing bounded/paged output, but it does not name or contrast any alternative tool such as get_full_sequence_info or get_sequence_structure.

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 only a pagination follow-up instruction ('Follow pagination.nextOffset for more'), not when to choose this tool over alternatives. With many sibling tools that also read sequence information, the description gives no conditions, exclusions, or prerequisites for selection.

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