List Project Job Titles

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

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive. The description adds that it returns a paginated JSON array with pagination metadata, and mentions the required project_id. This enriches the behavioral understanding.

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 reasonably concise at 6 sentences. The first two sentences are front-loaded with key purpose and usage. Some redundancy exists (e.g., mentioning pagination twice), but it remains efficient.

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 tool's simplicity, the description covers purpose, usage, parameters, and pagination behavior. Annotations provide additional safety cues. No output schema is needed here.

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%, so parameters are already described. The description adds value by explaining how page and per_page control pagination in this specific context, and re-emphasizes project_id as required.

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 returns a distinct list of job titles for contacts on a project, using specific verbs ('Return') and resource ('job titles for all contacts'). It distinguishes itself from numerous sibling list tools by focusing on this specific filter option.

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 explicitly instructs when to use the tool ('enumerate Directory records when you need a paginated overview, to find IDs, or to filter by query parameters'). It does not mention alternatives or when not to use it, but given the context, this is clear enough.

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