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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false); the description adds meaningful context beyond them by disclosing the corpus is built-in, finite (313 answers) and extracted from the product — i.e. curated, non-live content. It does not cover what a no-match returns or how many results come back, so it is not fully transparent.

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?

Two sentences, front-loaded with the core capability before the product framing. The 'Measure Tech PRO is a full CRM for contractors' clause is mild context-setting rather than pure waste, but it sits between the capability and the usage trigger.

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?

For a one-parameter, annotation-backed read tool with no output schema, the definition covers what the corpus is and when to query it. Only the shape of the response (single best answer vs. ranked matches) is left unstated.

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 coverage is 100% and the single 'query' parameter is already documented ('What the person wants to know, in their words'). The description only indirectly informs query construction via its topic list, so it adds little beyond the schema — baseline 3 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?

States a specific verb+resource ('Answers from the app's own built-in knowledge base') plus a concrete scope (313 support answers covering measuring, drawings, CRM, billing, troubleshooting). An agent can distinguish it from forum/pricing/overview siblings by domain, though no sibling is named explicitly.

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?

'Use this for how-do-I and does-it-do questions about...' gives a clear positive trigger with enumerated topic areas. It stops short of exclusions — e.g. it never says to prefer search_forum or get_pricing for community/pricing questions, leaving the sibling boundary to inference.

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