tpt_category_options

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

The description says 'Read,' implying a read-only operation, but the annotations set readOnlyHint=false and destructiveHint=true. This is a direct contradiction. The description also does not disclose any potential side effects or browser-state changes.

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 one sentence, front-loaded with the verb, and contains no filler. However, its brevity comes at the cost of important behavioral context, so it is efficient but not fully 'appropriate' in content.

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 and contradictory annotations, the description fails to explain return behavior, side effects, or the tool's role among many siblings. For a tool annotated as destructive, this is a significant and dangerous gap.

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 parameter 'field' has no description in the prose and schema description coverage is 0%. The enum values are provided in the schema, but the description does not explain how the tool's 'category options' relate to fields like Tax Code, Subject Area, or Format.

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 states a specific verb and resource: 'Read current category options from the TPT form.' The word 'current' and the category-options focus help distinguish it from sibling tools like tpt_choose_category, though it does not explicitly name alternatives.

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?

There is no guidance on when to call this tool versus siblings, no prerequisites, and no indication of whether it should be used before tpt_choose_category or during form preparation. The usage context is left entirely to inference.

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