Get Transcript IDs

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds 'Get all transcript IDs' but does not disclose additional behavioral traits like token usage, rate limits, or default pagination behavior. It matches annotations without contradiction.

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 a single concise sentence that is front-loaded with the core action. It is efficient, though could be slightly expanded to include the result nature without losing conciseness.

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 7 parameters (4 optional filtering parameters) and no output schema, the description lacks information about response format, pagination, and the meaning of 'transcript IDs'. It does not explain how to use the page range, status filter, or index/nValues parameters.

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 the schema already explains all 7 parameters (collId, id, pages, index, nValues, status, skipPagesWithMissingStatus). The description adds no parameter-level meaning beyond 'for a document'.

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 'Get all transcript IDs for a document' uses a specific verb ('Get') and resource ('transcript IDs for a document'), clearly distinguishing it from sibling tools like transkribus_doc_get_fulldoc or transkribus_doc_get_page_ids.

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 no guidance on when to use this tool versus alternatives, such as transkribus_doc_get_page_ids or transkribus_page_list_transcripts. No context or exclusions are mentioned.

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