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

The description says 'Refresh' but does not explain what that entails—e.g., whether it overwrites data, requires authentication, has rate limits, or is safe to call repeatedly. With no annotations provided, the description carries the full burden, and it fails to disclose side effects or constraints.

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 no unnecessary words. It is concise and front-loaded. However, it could be structured to include more contextual information without losing conciseness.

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?

Given no annotations, no output schema, and no parameters, the description is minimal. It lacks details on what the refresh entails, how it affects the system, and when it is appropriate to call. For a tool that likely has side effects (e.g., updating data), this is insufficient for an agent to use it safely.

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 input schema is empty (no parameters), so description does not need to add parameter-level details. Schema coverage is 100% vacuously. No additional information is required beyond what is already clear from the schema.

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 action ('Refresh') and the resource ('contract data from CanadaBuys'). It is a specific verb+resource combination. However, it does not explicitly distinguish from sibling tools like 'search_contracts' or 'get_contract_details', though the action type is different.

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. There is no mention of prerequisites, conditions, or when not to use it. The description simply states what it does without providing decision context.

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