hires_get_nurture_campaign

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

With no annotations provided, the description carries the full burden. It discloses that the operation retrieves a single campaign and includes all steps and configuration details, implying a read-only behavior. However, it does not explicitly state that it is read-only or mention any potential errors or permission requirements, which is a minor gap.

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 one sentence (13 words) and directly states the operation, target resource, and return contents with no fluff or redundancy.

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 single-get tool with one parameter and no output schema, the description covers the core behavior and what the response includes (steps and configuration details). It lacks explicit mention of error handling or authorization, but given the simplicity, the description is sufficiently complete.

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 already describes the single 'id' parameter with 100% coverage. The description reinforces that the campaign is fetched by ID but does not add any additional meaning such as format constraints or relationship to list tools. Schema coverage is high, so baseline 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 uses a specific verb 'Get' with the specific resource 'nurture campaign' and adds the detail that it returns 'all steps and configuration details,' distinguishing it from list_nurture_campaigns and other mutation 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 usage for fetching a single campaign by ID, but does not explicitly reference the list_nurture_campaigns tool as an alternative for finding IDs or contrast with create/update/delete. Usage context is clear but no exclusions or alternatives are provided.

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