camelot_contract_builder

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

Annotations already indicate idempotentHint=true and destructiveHint=false, so the description is not required to restate those. The description adds meaningful context: 'zero watermarks' highlights output quality, and 'Local browser processing' indicates privacy and processing location, which is not present in annotations. This goes beyond annotations and helps an agent understand side effects and constraints, earning a 4.

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 extremely concise: two sentences plus a canonical URL. It front-loads the primary purpose, then adds the unique selling points (zero watermarks, local processing) and a reference URL. Every part contributes useful information without redundancy. This is an example of efficient, well-structured documentation.

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?

The tool has an output schema, so return type is covered. The description covers core behavior, privacy, and watermark aspects. However, it does not mention the output format (e.g., whether the draft worksheet is a download, preview, or URL), which could be inferred from output schema but would be helpful to state. Given the tool's complexity (7 optional parameters) and the presence of annotations, the description is adequate but not fully exhaustive. A 4 is appropriate.

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?

Parameter descriptions in the schema have 100% coverage, so the baseline is 3. The tool description does not add any additional meaning to the parameters themselves; it only describes the overall function. Since schema is thorough, the description adds no extra value, but it also doesn't need to compensate, so a score of 3 is justified.

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 tool generates editable draft worksheets for consulting and services agreements, using specific verbs ('Generate', 'editable'). It distinguishes itself from generic 'contract' tools by specifying the deliverable, but does not explicitly differentiate from sibling tools like camelot_contractor_agreement or camelot_statement_of_work, which cover similar agreement types. The purpose is clear but sibling differentiation is missing, so a 4 is appropriate.

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?

No guidance is provided on when to use this tool versus alternatives. It does not specify scenarios, prerequisites, or exclusions. The name and description imply use for building contracts, but there is no explicit context about selecting this over camelot_contractor_agreement or camelot_statement_of_work. This is a significant gap for a tool with many close siblings.

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