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

With no annotations, the description discloses that the tool returns matching forms with citations and free fill-and-print URLs, which is key behavioral context. It doesn't mention rate limits or auth, but as a read-only search tool this is acceptable.

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?

One dense sentence that front-loads the tool's purpose, lists supported form types, and gives examples. No fluff, but it's a bit long; still efficient.

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 output schema, the description adequately states return content (citations and fill-and-print URLs). It covers the scope of forms and search capabilities, making it complete 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 fully describes query and limit. Description adds value by providing concrete alias examples ('FLHA', 'form 1.2', 'hot work'), enriching the meaning of the query parameter beyond 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?

Clearly states it searches Blue Crane's compendium of 126 Canadian contractor forms with specific scope (Ontario, Alberta, BC, Canada-wide). Uses specific verb 'Search' and resource 'compendium of contractor forms', distinguishing from sibling tools like get_form or list_categories.

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?

Provides clear context on what kinds of searches are supported (keyword, form number, alias) and gives examples, but does not explicitly contrast with siblings like get_form or which_form_do_i_need.

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