get_sdg_manifest

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

With no annotations, the description must carry behavioral disclosure, but it only says 'Return'. It does not clarify whether this is safe/read-only, how it behaves for non-terminal jobs, whether it can be called multiple times, or what 'managed artifact handles' imply for lifecycle/cleanup.

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?

A single sentence with no filler, and the core action/object is front-loaded. It is concise, though perhaps too sparse to be fully useful.

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 tool with no annotations, low parameter coverage, and a large SDG lifecycle context, the description omits preconditions, parameter semantics, and relationship to siblings. The output schema exists, but the description alone does not give an agent enough to invoke the tool correctly.

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%, and the description does not explain job_id, command_id, or idempotency_key. It only loosely matches the concept of job to job_id; the optional parameters are completely unexplained.

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 operation ('Return') and a specific resource ('terminal job manifest and managed artifact handles'), so an agent can tell it fetches a SDG job's final results. It does not explicitly contrast with get_sdg_job_status, but the name and 'manifest' wording give baseline differentiation.

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?

No guidance on when to call this versus get_sdg_job_status, read_artifact, or the SDG job lifecycle siblings. It says nothing about preconditions such as the job being terminal, nor when an alternative should be preferred.

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