find_objects

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

There are no annotations describing side effects, read-only status, or potential impacts. The description does not indicate whether the tool queries, modifies, or creates anything, so the agent cannot anticipate behavioral outcomes.

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 short and to the point, but its brevity sacrifices clarity. It is a single sentence without wasted words, yet it omits essential details and does not follow a clear 'verb + object' structure, making it less effective despite being concise.

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?

The description is incomplete for the given context. It does not mention the output format, return value, or any interaction with the system. Given the sibling tools, it is likely a query but lacks any information about what the caller receives or how to interpret results.

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 indirectly references 'class_name' by mentioning a 'short class name' but provides no detail about the 'limit' parameter. With zero schema descriptions for parameters, the agent has insufficient information about the meaning, constraints, or default behaviors of the inputs.

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 is a fragment, not a clear verb phrase. It mentions 'instances of a short class name' which implies finding objects, but it does not explicitly state the tool's function. The tool name 'find_objects' provides some clarity, but the description alone is ambiguous.

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 is provided on when to use this tool versus siblings like 'find_object' or 'list_types'. The description does not mention any conditions, prerequisites, or alternatives, leaving the agent to guess the appropriate context.

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