smb_search

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

No annotations are provided; the description only states it 'Returns matching records' from sources. It does not disclose behavioral traits like authentication requirements, rate limits, or what happens if no sources are connected. Transparency is minimal but not contradictory.

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 concise sentence followed by examples, front-loading the purpose. Every part is relevant and no redundant information is present.

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 tool with 3 parameters and no output schema, the description covers the basic functionality but lacks details on return format, pagination behavior (limit is mentioned but not explained), error handling, or prerequisites. It is adequate but could be more complete.

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%, so the description adds no extra value beyond the schema. It lists example sources in the text, which provides context, but does not elaborate on parameter usage or constraints beyond what the schema already contains.

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 clearly states the verb 'Search' and the resource 'all connected business data sources', with specific examples (Shopify, Stripe, QuickBooks) that distinguish it from sibling tools like smb_query or smb_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?

The description implies use when cross-source search is needed but does not specify when not to use it or provide alternative tools. Siblings like smb_query or smb_list_* might be alternatives for single-source queries, but this is not mentioned.

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