get_traceflow_result

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

Annotations already provide readOnlyHint, idempotentHint, and openWorldHint. The description adds that it gets current status and observations, reinforcing the non-destructive, idempotent nature. Does not add significant new behavioral context beyond what annotations indicate.

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?

Very concise: two sentences for description and an Args list. Front-loaded with purpose. No unnecessary words; every sentence earns its place.

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 read tool with no output schema, the description covers purpose, usage, and parameters adequately. It could mention return format, but given the tool's straightforward nature, it is reasonably complete.

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?

Zero schema description coverage, so the description must compensate. It explains traceflow_id as 'from a previous run_traceflow call' and target as 'Optional NSX Manager target name from config,' adding meaning beyond 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?

Begins with '[READ]' and clearly states the action (get) and resource (current status and observations of an existing Traceflow). It distinguishes itself from the sibling run_traceflow by specifying it checks a previously initiated one without waiting.

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?

Explicitly states use case: 'check a previously initiated traceflow without waiting.' Implies it should not be used to initiate new traceflows. Could explicitly mention not to use for new traces, but the sibling run_traceflow is present.

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