search_attachables

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

No annotations are provided, so the description must fully convey behavioral traits. However, it only states 'search with optional filters' without disclosing whether it is read-only, requires authentication, has pagination, rate limits, or any other behavioral characteristics. This is insufficient for safe and effective use.

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 that clearly states the tool's function. However, it sacrifices necessary detail for brevity; adding a bit more context would not reduce conciseness significantly.

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 the tool has nested parameters, no output schema, and no annotations, the description is too minimal. It does not explain what attachables are, the result format, or default behavior when no filters are provided. This leaves the agent without crucial context for correct invocation.

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?

The description adds no detail about the parameters beyond the schema. With schema description coverage at 50% (only the 'company' property is described at the top level), the description should compensate but only offers the vague phrase 'optional filters'. It does not clarify the purpose of 'file_name', 'content_type', 'limit', or the structure of the 'params' object.

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', the resource 'attachables', and the scope 'QuickBooks Online with optional filters'. It effectively distinguishes from sibling tools like create_attachable, get_attachable, etc., but does not elaborate on what attachables are, which is a minor gap.

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?

No guidance on when to use this tool versus other search tools like search_bills or search_customers. There is no mention of prerequisites, alternative tools, or context for preferring this tool over siblings.

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