Plant care profile

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

Beyond the readOnlyHint annotation, the description adds meaningful behavior: fields withheld by the configured plan are returned as null and named in `notes` rather than silently omitted. This is useful transparency about response shape, though it does not cover error cases or other edge behaviors.

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?

Two sentences, front-loaded with the core purpose and immediately followed by the most important behavioral caveat. No filler or repetition of structured metadata.

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?

With no output schema, the description compensates by enumerating the profile contents and explaining the null/notes handling for plan-withheld fields. For a single-parameter read-only tool, this is complete and actionable.

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 single `plant` parameter is already fully described in the schema, including accepted formats and the cost difference between an id and a name. The description adds no additional parameter-level meaning, so the schema carries the burden and baseline 3 is appropriate.

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?

Description states exactly what it does: 'Full care profile for one species' and enumerates concrete content areas (sun, water, hardiness zones, mature height, edibility, toxicity, pests). This clearly distinguishes it from siblings like search_plants, planting_window, and companion_check.

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 when to use it (when you need a full one-species care profile) and the schema parameter explains how to supply a plant via search_plants id or name. However, it does not explicitly state when to prefer plant_details over alternatives or when not to use it.

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