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

Annotations already declare this a safe, read-only, non-destructive operation, and the description is consistent with them. The description adds only the 'summary' output form and not details like the shape of results, what 'available' means, or response size, but the zero-parameter read-only nature keeps the gap modest.

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 filler and the action is front-loaded. For a zero-parameter tool, this length is appropriate.

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?

With no output schema and a short description, the tool's result contents and scope are underspecified. The phrase 'available contracts' is ambiguous, and given many similar siblings, the definition does not give an agent enough context to reliably select it.

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?

There are zero parameters and schema coverage is 100%, so there are no parameter semantics for the description to clarify. The 0-param baseline of 4 applies.

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 names a clear action ('Get') and object ('a summary of available contracts'), so the basic purpose is understandable. However, 'available contracts' is vague and the description does not distinguish this tool from siblings such as search_contracts, get_contract_details, or summarize_alberta_opportunities; the 'federal' scope only appears in the title.

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 offers no guidance on when to choose this tool over alternatives. It does not mention that search_contracts or get_contract_details should be used for filtered or detailed lookups, nor does it exclude Alberta-specific cases; selection is left entirely to inference from the name.

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