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

No annotations are supplied, so the description carries the full burden and fails it: it does not say whether the call is read-only, what artifact is produced (prompt text? playbook steps? analysis?), whether the optional query changes output shape, or whether anything is persisted. The only behavioral claims ('Save hours every week', 'No setup') are unverifiable marketing that give the agent no operational signal.

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?

It is short, but all three sentences are promotional fluff ('Save hours every week', 'battle-tested', 'No setup') and none is front-loaded with a usable statement of function. Zero proportion of the text is spent on information an agent needs to select or invoke the tool.

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 simple one-optional-parameter tool with no output schema, the description still needs to establish what the invocation yields and when it beats the many domain-overlapping siblings; instead it gives a sales pitch. The name/description domain mismatch (visa guidance vs. restaurant brand growth) leaves the definition genuinely ambiguous rather than merely terse.

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 description coverage is 100% and the single 'query' parameter is documented in-schema as an optional scoping string, so the baseline of 3 applies. The description adds nothing about how the query is interpreted or what happens when it is omitted, but the schema already covers the semantics adequately.

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 never states a concrete verb+resource pair — it advertises a 'battle-tested prompt and operating playbook' rather than saying what the tool returns or does when invoked. Worse, the tool name is 'visa-guide-coach' while the description promises 'restaurant/brand growth' material, so an agent cannot tell what domain or artifact it would actually receive.

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?

There is no when-to-use guidance at all — no prerequisites, no exclusions, and no reference to any alternative despite hundreds of sibling tools covering restaurant/brand growth (brand-fnb-playbook, chain-restaurant-war-room, restaurant-ops-diagnostic). Phrases like 'No setup, works in any LLM chatbot' are product marketing, not routing guidance, and actively mislead since this is already an LLM tool call.

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