read_compile

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds minimal context by specifying it reads a 'result', implying it's for completed jobs rather than real-time status. However, it doesn't disclose rate limits, authentication needs, or error behaviors beyond what annotations cover.

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, front-loaded sentence with zero waste. It directly states the action and target, making it efficient and easy to parse, though it could benefit from more detail given the tool's complexity.

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 the tool has annotations (readOnlyHint) and an output schema, the description is minimally complete. However, for a tool with 1 parameter (a nested object) and no schema descriptions, it should explain more about the compile process and result format to aid the agent fully.

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 has 0% description coverage, but the description implies parameters are needed to identify the compile job. It doesn't detail the 'model' parameter's structure or semantics, but since there's only one parameter (a nested object with projectId and compileId), the baseline is high. The description could compensate more by mentioning these IDs.

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 'Read a compile packet job result' states the verb ('Read') and resource ('compile packet job result'), but it's vague about what a 'compile packet job' entails and doesn't differentiate from sibling tools like 'read_backtest' or 'read_optimization'. It's adequate but lacks specificity about the domain context.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'create_compile' and 'read_backtest', it's unclear if this is for retrieving results after compilation or for monitoring ongoing jobs. No explicit when/when-not statements or prerequisites are mentioned.

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