get_workflow_notifications

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

With no annotations, the description carries the transparency burden. It describes the return format and notification semantics but does not explicitly state that the operation is read-only, side-effect-free, or any authorization requirements. The name 'get' implies safety but this is not disclosed in the text.

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 well-organized with a clear purpose statement, a brief conceptual note, and structured Args/Returns sections. Every sentence adds value, and the length is appropriate for the information conveyed.

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?

For a simple get tool with two parameters, the description covers the operation's purpose, parameter semantics, and return structure. It also provides context by contrasting with events. It lacks explicit error handling or auth notes, but these are not critical for this straightforward read operation.

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%, so the description must add meaning. The Args section provides clear semantic labels ('Name of the DBOS application', 'ID of the workflow') that go beyond the bare schema titles. It does not include examples or formats but sufficiently compensates for the schema gap.

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 opens with 'Get notifications received by a workflow from DBOS Conductor,' which is a specific verb+resource. It further distinguishes itself from events by explaining that multiple notifications can be sent on the same topic, differentiating it from sibling tools like get_workflow_events.

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 explains the conceptual difference between notifications and events, implying when this tool is appropriate. However, it does not explicitly name an alternative tool or provide clear when-not-to-use guidance, so it falls short of a 5.

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