Get All Job Titles Belonging To A Group

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

Annotations (readOnlyHint=true, idempotentHint=true) already inform the agent this is a safe read. The description adds 'returns an array of Job Titles' but also incorrectly says 'returns a JSON object describing the requested Resource Planning records', which could mislead. Minimal added value, but no contradiction.

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 includes unnecessary or confusing sentences (e.g., 'Use this to fetch the full details of a specific Resource Planning records by its identifier') and endpoint details that are likely not helpful. It could be more concise and focused.

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?

With no output schema, the description should clarify the return format. It states 'Returns an array of Job Titles' but then contradicts with 'JSON object describing the requested Resource Planning records'. Pagination parameters (page, per_page) are not mentioned. Incomplete for a tool with multiple params and no output schema.

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% with descriptions for all 4 parameters. The description mentions required parameters but adds no new meaning beyond what the schema already provides. Baseline 3 for high coverage.

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 tool name clearly indicates it returns job titles for a group, but the description is confusing: it mentions 'fetch the full details of a specific Resource Planning records by its identifier' which is inconsistent (it returns an array, not a single record, and no single identifier is used). This reduces clarity.

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 explicit guidance on when to use this tool vs alternatives like get_a_single_job_title or other job title tools. The description does not differentiate from siblings or provide context on appropriate usage.

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