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

While operational hints (readOnlyHint, destructiveHint) are covered by annotations, the description adds significant behavioral context by listing the contents of the response, such as 'what it looks like, common causes, what to do first, and its sources.' This gives the agent a richer expectation of the data provided.

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 tool definition is highly concise and well-structured. It front-loads the core action and content description, efficiently linking the tool's function to its required input (slug from search_guides) without any fluff.

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 only two parameters, the definition is exceptionally complete. It covers the operational constraints (no sign-in), the input dependency (search_guides), and the detailed content of the expected output.

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?

Since the schema description coverage is 100%, the parameter semantics are already highly defined by the structured data. The description does not introduce new parameter meaning but rather contextualizes the type of data the parameters will access.

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 identifies the resource (LeafSight plant problem guide) and the action (Read... in full), distinguishing it from other potential plant interaction tools. It specifically instructs the user on the necessary prerequisite data source ('Use a slug from search_guides').

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 definition provides critical usage context by stating 'No sign-in needed' and mandates that the slug must originate from 'search_guides.' This clear prerequisite knowledge guides the agent's workflow effectively.

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