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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It fails to mention that non-GET requests can have side effects, that confirm must be true to execute a live change, or that dry_run is available for preview. The schema includes these safety features, but the description itself does not set expectations about mutating behavior or confirmation requirements.

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, well-structured sentence that immediately conveys the tool's purpose. There is no filler or redundant content; every word earns its place.

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 tool has 7 parameters, nested objects, a generic endpoint-calling scope, and no output schema. The one-sentence description does not explain the request/response format, error behavior, or how the confirm/dry_run fields interact with the saved connection details. Given the tool's flexibility, more context about advanced usage and fallback scenarios is needed.

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 schema descriptions cover 86% of parameters, including detailed explanations for confirm, dry_run, body_json, query_json, and headers_json. The description adds no parameter-level information beyond what the schema already provides, so the baseline of 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 states the tool's function: use any documented Teamtailor Ops Control Plane endpoint via the buyer's saved connection details. This distinguishes it from specific sibling tools like create_candidate or list_jobs, which target individual resources. The verb 'use' plus 'any documented endpoint' makes the scope explicit.

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 phrase 'any documented endpoint' implies it can be used when no specific tool exists, but it never explicitly says 'prefer the specific tools when available' or 'use only for endpoints without a dedicated function.' The guidance is implied, not stated, so it lacks clear when/when-not direction.

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