company_contractors

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

No annotations are provided, so the description must disclose behavior. It mentions 'advance' which implies mutation, but doesn't explain what actions occur, side effects, or required context. Terms like 'scoped chain lifecycle' are opaque. The behavior is not transparent.

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?

One sentence with no filler, front-loading the action. However, it is cryptic and uses jargon that hurts clarity. Still, it is appropriately brief.

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 7 parameters, no schema descriptions, no annotations, and an output schema that is not described, this one-line description is grossly insufficient. It does not explain operation modes, required inputs, or what 'advance' entails. The agent cannot reliably invoke this 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?

Schema has zero parameter descriptions, and the description mentions none of the seven parameters. The agent gets no clue about what project_id, bundle_json, operation, or payload_json mean or how to populate them. This is a critical gap.

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?

States a clear verb-resource pair: 'Inspect or advance contractor engagements'. This distinguishes it from most sibling tools, though the phrase 'scoped chain lifecycle and verified receipts' is ambiguous. The core purpose is discernible but not fully elaborated.

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?

No guidance on when to use this tool versus alternatives. The description gives no context about specific scenarios, exclusions, or prerequisites. An agent would have to infer its applicability from the name alone.

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