get_contracts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'List all contracts' and repeats parameter names, without mentioning read-only status, pagination behavior, permissions, or limits. The meaning of 'all' is ambiguous given pagination parameters.

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 concise and well-structured: the main action 'List all contracts' is front-loaded, followed by clear parameter definitions. Every word serves a purpose, with no redundant or filler content.

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 description is too sparse for the tool's context. Although an output schema exists, the description fails to explain that results are paginated, how to request specific pages, or whether any filtering is possible. It also lacks any usage guidance or alternates, leaving the agent without sufficient context to choose this tool appropriately.

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 schema has 0% description coverage, so the description must compensate. It defines 'page' as 'Page number' and 'per_page' as 'Results per page', which adds minimal semantic meaning beyond the schema titles 'Page' and 'Per Page'. This is a slight, albeit minimal, compensation for the lack of schema descriptions.

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 'List all contracts' with a specific verb and resource. It distinguishes from the sibling tool 'get_contract_by_id' by indicating a list operation rather than retrieving a single contract.

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 about when to use this tool versus alternatives. There is no mention of using 'get_contract_by_id' for fetching a single contract, nor any discussion of filtering or conditions that would make this tool appropriate.

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