get_engine_status

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

No annotations are provided, placing the full burden on the description. The two-word description gives no behavioral traits such as whether the operation is read-only, has side effects, or any access requirements. This is insufficient for an agent to infer safety or consequences.

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 extremely concise (two words), which makes it front-loaded and efficient. However, it lacks explanatory context about what 'engines' are, which could lead to ambiguity. A slightly longer description would not harm conciseness and would improve clarity.

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 no parameters and an output schema exists, the description is adequate but not complete. It states the action but does not explain the meaning of 'engines' or the structure of the output. The output schema presumably covers return details, so the description is minimally sufficient.

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 tool has zero parameters, and the schema coverage is 100% (empty properties). The description adds no additional parameter information, but with no parameters, the schema already fully defines the interface. A baseline of 4 is appropriate as the description doesn't need to compensate.

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 'Show available engines' clearly specifies the verb (Show) and resource (available engines), making the tool's purpose immediately understandable. However, it does not differentiate from sibling tools, many of which also use 'get' or 'show' verbs, but 'engines' is unique enough to avoid major confusion.

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. It does not mention any prerequisites, exclusions, or context in which this tool is preferred over sibling tools like 'get_job_details' or 'search_jobs', which leaves the agent without directional help.

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