Retrieves The Status Of The Asyncronous Job That A Bulk Users Command Queued

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description is not burdened to state these. The description adds that it returns a JSON object and gives API endpoint details, but does not elaborate on pagination or response structure beyond what schema provides. It adds moderate value.

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 paragraph with multiple sentences, front-loading the purpose and then providing API details. It is efficient with no wasted words, though it could be slightly more structured.

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 details about the return value structure (e.g., pagination, fields included) and does not fully compensate for the absence of an output schema. Annotations cover safety and idempotency, but more context on the response would improve completeness.

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?

Input schema has 100% coverage with descriptions for all parameters. The description lists required parameters but does not add additional meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 specifies the verb 'retrieves' and the resource 'status of asyncronous job from bulk users command'. It also clarifies that it reads Directory records, distinguishing it from other tools that might create or update bulk users.

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 states 'Use this to read information about Directory records from Procore', which provides clear context for when to use this tool. However, it does not explicitly mention when not to use it or provide alternatives, though its specific purpose reduces ambiguity.

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