camelot_nda_generator

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

The annotations already indicate idempotent, non-destructive behavior. The description adds useful context beyond those annotations by stating the tool runs through 'Local browser processing' and frames the output as a 'draft worksheet,' clarifying the non-final nature of the artifact. There is no contradiction with the annotations.

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 core purpose is front-loaded in a single sentence, and the local-processing and canonical URL lines add light context without bloat. Minor formatting issues like the double period after 'worksheets' prevent a perfect score.

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?

With an output schema, rich annotation metadata, fully documented optional parameters, and a clear description of the generated artifact, the agent has enough to invoke the tool correctly. The main missing piece is usage routing relative to sibling tools, but that is already penalized in the usage guidelines dimension.

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 has 100% description coverage, with all six parameters documented and default values provided. The description itself adds no parameter-level semantics beyond what the schema already supplies, so the baseline score of 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 clearly states a specific verb and resource: 'Create customizable mutual or unilateral NDA draft worksheets.' The NDA focus distinguishes it from broader siblings like camelot_contract_builder, though it does not explicitly name an alternative. It is specific and actionable, but the 'Non-Disclosure Agreement Template' prefix is partially redundant with the title concept.

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?

There is no guidance on when to use this tool versus related document tools such as camelot_contract_builder, camelot_contractor_agreement, or camelot_terms_of_service_template. 'Local browser processing' is a behavioral detail rather than a usage condition, and no exclusions or alternative routing are provided.

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