get_transcript

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

No annotations are supplied, so the description carries the full load. It usefully discloses the returned content categories (messages, replies, tool activity, errors) and a pagination mechanism, which are real behavioral facts. It omits ordering, whether the call is read-only, default/maximum limits, and what happens when after_event_id exceeds the log.

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 tight sentences with the content summary front-loaded and the pagination note trailing. Nothing is wasted, though 'Page with after_event_id' is terse to the point of being cryptic about direction and exclusivity.

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 no annotations and no output schema, the description has to do more work than it does. It covers what the transcript contains and one pagination parameter but leaves limit semantics, ordering, and the shape of returned events undefined.

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 0% across three parameters, so the description must compensate and largely does not. Only after_event_id gets any explanation ('Page with after_event_id'); limit and agent_id are left entirely to their bare schema titles.

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 resource and its contents: 'the agent's conversation log: your messages, its replies, tool activity and errors.' That is far more informative than the name alone and implicitly distinguishes it from the app-conversation siblings by scoping to a single agent. It stops short of naming an alternative tool explicitly.

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?

There is no when-to-use or when-not-to-use guidance, and no routing against siblings like read_app_conversation or list_app_conversations. The only usage hint is 'Page with after_event_id', which addresses iteration rather than selection.

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