Fetch the status and details of a Raven creative generation job by its ID.
Read a Raven creative generation job by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Generation job ID. |
Changes observed during successful MCP inspections.
v2.2.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the read-only, idempotent, non-destructive profile, which matches the description. The description adds resource context but does not disclose other behaviors like error responses or whether the job may be returned partially. With annotations covering the safety aspect, a 3 is appropriate.
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, well-structured sentence that front-loads the action and resource with no redundancies. Every word 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?
This is a simple one-parameter read operation with no output schema and robust annotations. The description is complete enough to guide invocation behavior—knowing the tool retrieves a single generation job by ID. Any additional detail about return payloads would be redundant here.
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 describes the only parameter 'id' as a generation job ID with 100% coverage. The description merely reinforces 'by ID' and does not add extra value beyond what the schema already provides.
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 uses a specific verb, 'Read', with a clear resource, 'Raven creative generation job', and specifies the identifier dimension 'by ID'. This cleanly distinguishes it from sibling tools like create_generation_job and list_generation_jobs, which imply different scopes and actions.
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 implies usage by ID, but it does not explicitly state when to prefer this tool over alternatives such as list_generation_jobs or create_generation_jobs. The guidance is only implicit through the word 'by ID', and no alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.