timps_contract_reviewer

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

No annotations are provided, so the description is the sole source of behavioral info. It discloses that it returns a scorecard and redline, but does not state whether the operation is read-only, requires any permissions, or has side effects. For a 'reviewer' tool, safety is implied but not explicit, which is a moderate gap given the absence of 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 description is a single, well-structured sentence that front-loads the primary action (review a contract) and lists specific red-flag categories, followed by a clear output statement. Every phrase adds value, with no redundancy or filler.

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 no output schema, so the description must explain return values; it mentions 'clause-by-clause scorecard and a redline' but lacks detail on the structure or format. It also doesn't explain how the contract is provided (presumably via the request parameter). Overall, it gives a solid overview but could benefit from more specifics on inputs and outputs.

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 baseline is 3. The description does not add extra meaning to the parameters, but it doesn't need to since the schema adequately describes 'request' and 'language'. However, the 'language' parameter seems irrelevant to contract review and is unexplained in the description, slightly reducing clarity but not enough to drop below baseline.

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's purpose: review contracts (MSA, NDA, SaaS, vendor agreement) for specific red-flags (indemnification, liability caps, IP, data, termination, SLAs) and returns a clause-by-clause scorecard and redline. This is a specific verb+resource with concrete scope, distinct from generic tool descriptions.

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 context by listing contract types and red-flag areas, but does not explicitly say when to use this tool vs. alternatives (e.g., timps_api_contract_auditor or timps_license_compliance_scanner). There are no exclusions or alternative recommendations, but the context is clear enough for likely use cases.

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