beta_recruitment_criteria__create

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

Annotations indicate it's not readOnly, idempotent, or destructive, but it's a creation. The description mentions 'POST' implying mutation, but no additional behavioral traits (e.g., whether it requires specific permissions, side effects, return 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?

Short and to the point, but could be more informative without being verbose. Includes the HTTP path, which is helpful.

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 the nested input schema and no output schema, the description lacks details such as what the tool returns, error conditions, or additional constraints. Incomplete for confident agent invocation.

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 coverage is 100% for the single parameter 'body', and the description adds 'JSON:API request body (Apple schema: BetaRecruitmentCriterionCreateRequest)', which clarifies the format. However, no further details on parameter semantics beyond what schema provides.

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 'Create a beta recruitment criteria' clearly states the verb and resource, and the HTTP method is provided. However, it does not differentiate when to use this over sibling create/update/delete tools, but the name and context suffice.

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 vs alternatives like beta_recruitment_criteria__update or delete. No context on prerequisites or typical use scenarios.

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