Create A Job Title

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

Annotations already indicate it's a write operation (readOnlyHint=false) and non-destructive. The description adds that it returns HTTP 201 and the created object, but does not disclose auth requirements, rate limits, or side effects. Thus, it adds minimal value beyond annotations.

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 relatively concise but contains slight redundancy (repeats 'Resource Planning records' twice) and a grammatical error ('records' instead of 'record'). It could be tighter, but it is functional.

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 covers the basic purpose, required parameters, and API endpoint. However, it lacks details on return object structure (no output schema) and prerequisites (e.g., company must exist). For a create tool with no output schema, it is adequate but not comprehensive.

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 input schema covers 100% of parameters with descriptions. The description lists the required parameters but does not add new meaning beyond what the schema already provides. Baseline score 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 it creates a new Job Title in a specified company and mentions it's for Resource Planning records. It provides the API endpoint, which adds specificity. However, it does not explicitly differentiate from sibling tools like 'update_a_job_title' or other create tools, so it scores a 4 rather than a 5.

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 says 'Use this to create a new Resource Planning records' but provides no guidance on when not to use it, alternative tools, or prerequisites (e.g., company must exist). The usage context is implied but lacks explicit exclusions or alternatives.

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