autotask_search_contracts

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

No annotations are provided, so the description must cover behavioral traits. It mentions filtering but does not disclose pagination behavior (pageSize defaults are documented in the schema), response structure, or any side effects. However, since the schema covers pageSize fully, the description adds no meaningful behavioral context beyond the schema.

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 8 words, which is concise and front-loaded. It contains no unnecessary words, but could benefit from slightly more detail without being verbose.

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 4 optional parameters and no output schema. The description is minimal but sufficient given that all parameters are documented in the schema. However, it lacks explanation of return behavior or result format, making it slightly incomplete for a search tool.

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% (all 4 parameters have descriptions). The description says 'optional filters' which adds no new meaning beyond what the schema provides. Therefore 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 clearly states this tool searches for contracts with optional filters. The verb 'Search' and resource 'contracts' convey the purpose, and it distinguishes itself from sibling create/get/update tools for contracts.

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 this is for searching contracts, but provides no guidance on when to use this versus other search tools (e.g., autotask_search_quotes, autotask_search_invoices). It doesn't specify when not to use this tool.

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