Search plants

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions the endpoint and the broad matching scope, but omits important traits such as pagination, read-only nature, default limits, or result format. This leaves significant gaps for an agent.

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 plus an endpoint note. It is front-loaded with the key action and scope, wasting no words.

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 lack of output schema and only two parameters, the description covers the basic purpose and endpoint. However, it fails to mention what the search returns (e.g., full plant objects or IDs), pagination behavior, or sorting defaults. This leaves the agent with incomplete context for using the tool effectively.

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 parameter descriptions already define syntax. The tool description adds value by explaining that 'expression' is a free-text search across multiple fields, but does not add additional context for the 'limit' parameter. Overall, it provides marginal improvement over the schema.

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 resource 'plants', and specifies that it matches multiple fields (name, location, attributes and more). This distinguishes it from sibling tools like 'list_plants' which likely provides a simple listing.

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 explains what the tool does but does not provide guidance on when to use it versus alternatives like 'list_plants'. There is no explicit when-to-use or when-not-to-use context, making it adequate but lacking in decision support.

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