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

With no annotations, the description fully carries the behavioral burden. It explicitly discloses the critical behavior that this MCP does not write local files, clarifying that it returns metadata only. This is a significant and non-obvious trait that would otherwise be unknown to the agent.

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 a single, concise sentence that front-loads the core purpose and adds a crucial behavioral clarification. Every word earns its place, with no unnecessary filler.

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?

Given that an output schema exists and the tool is relatively simple, the description covers the essential purpose and behavioral nuance. It could benefit from a bit more context on what 'metadata' includes or how to retrieve the actual artifact, but the output schema likely handles return details, so this is adequate.

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 compensate for parameter meaning. However, it does not mention job_id or artifact_id at all, leaving the agent to infer their roles from the names alone. This fails to add any value beyond the schema's basic 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?

The description clearly states the tool returns artifact download metadata and content hash, specifying the verb (return) and resource (artifact download). This distinguishes it from siblings like hydracept_job_status or hydracept_get_receipt, which focus on other aspects of job or receipt information.

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 when an agent needs artifact metadata or content hashes, but it does not explicitly mention when to use this tool over alternatives or any exclusions. The 'hosted MCP does not write local files' note hints at a key behavioral consideration but is not framed as a usage guideline.

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