enroll_candidate

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

With no annotations provided, the description must disclose behavioral aspects. It conveys that this is a mutation (enrolling), but fails to mention side effects such as creation of candidate records, idempotency, whether it overrides existing enrollments, implications of the 'send_email' parameter, or required permissions. The one-line description is not misleading but leaves most behavioral details undisclosed.

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 extraneous words, so it is concise. However, it is under-specified to the point of being minimal, which is more an issue of completeness than conciseness. It is structured logically (verb + object), but the brevity does not serve the agent's needs.

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 tool with 5 parameters, 2 required, and no output schema, the description is far from complete. It omits explanation of key parameters, expected behavior, and any side effects or requirements. An agent would have to guess the meaning of 'slug' and 'send_email', and would not know what to expect as a result. This is insufficient for reliable tool invocation.

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 0% and the schema itself contains no property descriptions. The description adds no meaning for any of the five parameters. It doesn't explain that 'slug' likely refers to the pipeline slug, that 'email' identifies the candidate, or what 'send_email' controls. Since the schema is silent, the description must carry the load and it completely fails to do so.

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 states a specific verb ('Enroll') and resource ('candidate' in a 'pipeline'), which clearly conveys the core action. It distinguishes itself from sibling tools like list_pipelines or get_pipeline_enrollment by implying a write operation, though it doesn't explicitly contrast with any sibling. The purpose is clear and not tautological, but lacks specificity about which pipeline or how candidates are identified.

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 provides no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. For example, it doesn't indicate that the pipeline must exist or that a candidate might already be enrolled. The agent is left to infer usage from the name alone, which is insufficient for a non-trivial mutation.

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