hires_list_nurture_campaigns

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

With no annotations provided, the description carries the burden. It discloses that results are summaries including steps, which is useful. However, it does not mention pagination limits, default sorting, or confirm read-only behavior. 'List' implies non-destructive but this is not explicit.

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 two short sentences, immediately states the action, and avoids unnecessary detail. Every word contributes value.

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?

For a simple list tool with no output schema and no annotations, the description provides the core function and return content. It could mention the scope (e.g., all nurture campaigns for the company) but the schema covers company_id optionality. Overall it is sufficiently complete for this straightforward operation.

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 description coverage is 100%, so all parameters are already explained. The description adds 'pagination' context and mentions summaries, but this is largely redundant with the schema. It does not significantly deepen understanding of page/size/company_id beyond their existing descriptions.

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 'List nurture campaigns with pagination', using a specific verb and resource. It also notes that it returns summaries including steps, which distinguishes it from a 'get' operation and from other list tools.

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 implies this tool is for listing nurture campaigns, but does not explicitly state when to use it instead of alternatives like get_nurture_campaign or other list tools. No exclusions or alternative guidance is provided.

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