list_category_parameters

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

No annotations are provided, but the description discloses the return behavior: 'Returns each parameter with its type and a sample value.' The verb 'list' implies a read-only operation, and no side effects or prerequisites are mentioned. While it doesn't explicitly state 'read-only' or address edge cases, the transparent return format compensates for the absence of annotations.

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 three sentences plus an Args line, front-loaded with the core purpose, followed by return details and usage guidance. Every sentence adds value without redundancy.

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?

Given a single parameter and no output schema, the description fully covers what the tool does, what it returns, and when to use it. The explicit mention of return content (type and sample value) makes the tool's behavior complete for its simplicity.

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 only parameter, category_name, is explained with 'Revit category, e.g. "Walls", "Doors", "Rooms".' This adds concrete examples and domain context beyond the schema's bare string type, fully compensating for the 0% schema description coverage.

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 uses the specific verb 'List' and identifies the resource as 'parameters available on elements of a category', clearly distinguishing it from sibling tools like list_family_categories or list_revit_views. It is unambiguous and immediately understandable.

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 explicitly states 'Use this to find a valid parameter_name for color_splash, and to check what modify_elements can set on a category', naming specific sibling tools and concrete use cases. This provides clear guidance on when to use this tool versus alternatives.

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