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

Beyond the 'readOnlyHint' annotation, the description provides critical behavioral context regarding the return data: a successful job is indicated by the presence of an 'absolute, temporary download URL.' This is vital operational knowledge for 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 highly concise, consisting of two efficient sentences that front-loads the resource type and the key benefit of the 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?

For a read-only status check, the definition is highly complete. It identifies the resource, the action, and explicitly defines what the successful output will contain, giving the agent all necessary context to use the tool.

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?

With 0% schema coverage, the description lacks semantic detail regarding the 'job_id' itself (e.g., format or expected structure). Since the schema is extremely thin, the description cannot significantly compensate, resulting in a baseline 3.

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 it checks the status of an 'XML.now conversion job.' This is a precise verb+resource combination that effectively differentiates it from list-based sibling tools.

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 detailing the outcome of a 'completed job' (a temporary download URL). However, it does not provide explicit guidance on when to use this status check versus, for example, initiating a conversion using a different tool.

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