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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds domain context by explaining the possible enrollment states and the recorded agreement rate, but says nothing about auth requirements, refresh timing, or what happens when enrollment was never decided.

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?

A single front-loaded sentence that states the resource, enumerates the possible states, and ends with the read-only marker. No wasted phrasing.

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 low-complexity read tool with an output schema and safety annotations, the description is nearly sufficient: it names the resource, the possible states, and the agreement-rate field. It is only missing when-to-use routing against the many sibling rule/categorization tools.

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% and there is only one required parameter (companyId), so the schema already carries full parameter semantics. The description only says the read is 'for a company' and adds no format or meaning beyond that.

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 (Read) and resource (categorization rule engine enrollment state for a company), and enumerates the meaningful states (shadow, enabled, off) plus the agreement rate. It does not name a sibling alternative, but an agent can distinguish it from the many transaction_* rule tools by its enrollment/mode focus.

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 the tool is for checking a company's rule-engine mode, but gives no explicit when-to-use guidance, no prerequisites, and no alternatives (e.g., transaction_get_categorization_rule or transaction_get_list_categorization_rules). Usage must be inferred.

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