camelot_terms_of_service_template

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

Annotations indicate idempotentHint=true and destructiveHint=false, so the description doesn't need to cover those. The description adds 'Local browser processing' which is useful behavioral context. However, it doesn't disclose what the output looks like or whether the tool generates a downloadable document, which would be helpful for a template generator.

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 two sentences and front-loads the core purpose. The canonical URL is useful but could be considered extra; still, it's compact and every sentence earns its place.

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 and all parameters are documented, so the description doesn't need to explain return values. However, for a template generator, it would be helpful to mention what kind of output is produced (e.g., a worksheet, a document) and whether it's a draft for review. The description is adequate but not rich.

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 100%, so the schema already documents all four parameters. The description adds no parameter-specific meaning beyond what the schema provides, so the 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 states a specific verb ('Draft') and resource ('website and SaaS terms of service worksheets') and mentions coverage of user conduct and liability. It is clear what the tool produces, though it doesn't explicitly distinguish itself from the sibling camelot_privacy_policy_template or camelot_contract_builder beyond the resource type.

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 the tool is for generating terms of service worksheets, and the canonical URL adds context. However, it does not state when to use this tool versus alternatives like camelot_privacy_policy_template or camelot_contract_builder, nor does it mention any exclusions or prerequisites.

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