vibemk_get_discovery_background_job

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

There are no annotations and the description does not explicitly state that the operation is read-only or side-effect free. It says 'Show' but does not disclose whether it polls, triggers anything, or requires certain permissions.

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 and front-loaded, using a single sentence and an emoji. It contains no fluffy or redundant information, fitting the simple one-parameter operation.

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?

The description lacks context about the discovery workflow, such as what the returned job status looks like, whether it is the latest job or a specific job ID, or how it relates to other discovery tools. The lack of an output schema and any explanation of return values leaves significant ambiguity.

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 only parameter, host_name, is described with a clear purpose ('Host name to check background job status'). However, no additional details are given about expected format, case sensitivity, or validation, so it only minimally exceeds the schema.

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 indicates the tool is for retrieving discovery job status for a host, distinguishing it from other discovery-related tools that start or wait for discovery. The verb 'Get' and resource 'discovery background job' are specific, though 'last' adds some ambiguity.

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 the many similar discovery-related siblings (e.g., get_discovery_status, start_service_discovery, wait_for_discovery). It does not mention whether this returns historical or current status, nor any prerequisites.

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