Get Current Transcript

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating a safe read operation. The description adds no behavioral context beyond these annotations. It does not mention possible outcomes (e.g., what happens if no transcript exists) or return format. Given that annotations cover basic traits, the description meets a minimum threshold but adds no extra value.

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 sentence that is concise and to the point. It front-loads the core purpose. However, it could be slightly more informative without losing conciseness (e.g., mentioning the return type). For its length, it is effective but not maximally helpful.

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 that the tool has no output schema, the description should compensate by explaining the return value (e.g., transcript text, format). It also omits error conditions (e.g., page not found, no current transcript). The presence of many sibling tools with similar purposes demands more contextualization to avoid confusion. The description is too minimal for an agent to use reliably.

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?

The input schema provides descriptions for all three parameters (collId, id, page) with 100% coverage. The description adds no additional meaning, explanation, or examples beyond the schema. With high schema coverage, the baseline is 3, and the description does not compensate or enhance.

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 the current transcript for a page' clearly specifies the action (Get) and resource (current transcript). The verb 'Get' and noun 'current transcript' are specific, and 'for a page' clarifies scope. However, it does not differentiate from sibling tools like 'transkribus_page_get_transcript', which might retrieve a specific transcript. The name includes 'curr' to imply 'current', but the description offers no contrast.

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 over alternatives. There are no explicit 'when to use' or 'when not to use' statements. Sibling tools like 'transkribus_page_get_transcript' may serve a similar purpose, but the description does not explain the difference. Context signals (e.g., the presence of many sibling tools) heighten the need for usage guidance.

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