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

Annotations already establish this as a safe, idempotent read (readOnlyHint/idempotentHint true). The description adds value beyond them by describing the shape of what comes back (fields, regions, bid_critical_details optional questions) and a hard behavioral constraint (never guess an answer), though it omits error cases such as an unknown petal_id.

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?

Purpose is front-loaded in the first clause, followed by ordered usage rules; every sentence carries an instruction. It is dense but not padded, and nothing is restated.

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?

There is no output schema, so the description must carry the return-value burden, and it does name the key returned structures (fields, regions, bid_critical_details). For a one-parameter read tool with full annotation coverage, that is sufficient, with only minor gaps around error handling.

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?

With 100% schema description coverage and a single parameter, the schema already documents petal_id as the category id from find_category. The description repeats that sourcing without adding format, range, or failure semantics, so the baseline 3 applies.

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?

States a specific verb and resource: retrieving the fields and regions for a Bidit category, and names the source of its input (petal_id from find_category). It is clearly distinguishable from the request-lifecycle siblings, though it never explicitly says which sibling to prefer over it.

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?

Gives concrete usage rules: ask the customer for required fields not already known, use listed options for select fields, and ask at most 3 unanswered bid_critical_details questions in order without guessing. It provides strong operational context but does not name an alternative tool or an exclusion case.

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