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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds a useful behavioral detail by saying the result includes 'all steps and schedule settings,' but it does not go further into response shape, pagination, or error behavior.

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 a single sentence with no filler. It front-loads the action and resource, then adds the most important detail about what is returned, which makes it easy to scan.

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 one-parameter read-only tool, the description covers the essential information: which resource is fetched and what is included. There is no output schema, but the phrase 'all steps and schedule settings' partially describes the return content. It leaves out error/not-found behavior, but that is a minor gap for a context of this complexity.

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 single required 'id' parameter has no schema description, and the description doesn't explicitly document it. The tool name and the phrase 'a nurture campaign' make it inferable that id identifies the campaign, but the description itself adds little direct parameter-level meaning.

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 action: 'Get a nurture campaign' with the specific resource, and even narrows the return content to 'all steps and schedule settings.' It distinguishes itself from the list sibling (hires_list_nurture_campaigns) by emphasizing a single campaign with full detail.

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 is for fetching one specific nurture campaign by id, which is reasonably clear from the singular 'a nurture campaign.' However, it never explicitly names an alternative like hires_list_nurture_campaigns for listing many campaigns, nor does it state when not to use this tool.

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