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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so 'Read-only; takes no arguments' largely restates structured data. The genuine value-add is the verbatim-pass-through rule, which warns the agent not to paraphrase or normalize the returned value — a real failure mode. It does not describe the shape of the returned list, but the output schema covers that.

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?

Three short sentences, zero filler: purpose first, then the workflow, then the read-only note. Every sentence carries distinct information and the actionable instruction is front-loaded.

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?

An output schema exists, so return-value detail is not required, and the description supplies the one thing the schema cannot: what to do with the results. Only minor gap is no hint about how large the list is or whether it is exhaustive, which affects how the agent should present candidates.

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%, so both optional analytics parameters are fully documented in the schema, and the 0-required baseline applies. The description adds nothing about `context` or `llm_model`, and 'takes no arguments' is mildly imprecise given two optional params exist — though it correctly signals no substantive input is needed.

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 and resource ('Lists the industries a company can be filed under') with the scoping detail that this is the enumeration used for company filing. It is unmistakably distinct from save_company_details and the other siblings, which all deal with company records rather than the reference list.

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?

Gives an explicit multi-step usage pattern: match the user's business description against the list, offer 3-5 closest entries, and pass the chosen value verbatim as `industry` to save_company_details. The downstream sibling and the condition for calling it are both named, leaving nothing to inference.

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