Get All Equipment Categories (Company)

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

Annotations already declare readOnlyHint=true, so the safety profile is clear. The description adds pagination behavior and response format, but the incorrect statement about fetching specific equipment records undermines transparency. It does not contradict annotations but misleads about the tool's actual function.

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 short but includes a contradictory and incorrect sentence that does not earn its place. The structure places the clear purpose first, but the following sentence adds confusion rather than value.

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?

The description mentions pagination and required parameters but omits the filter parameter and provides incorrect information about fetching specific records. Without an output schema, more clarity on response details is needed. The misinformation makes it incomplete.

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 coverage is 100%, so the baseline is 3. The description adds context for page and per_page (pagination control) and notes required parameters, but does not mention the filters__is_active parameter. It adds some value but not comprehensive.

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 initially states 'Get all equipment categories (Company)' which clearly identifies the resource, but the next sentence says 'fetch the full details of a specific Equipment records by its identifier,' contradicting the tool's purpose and causing confusion. This mix-up reduces clarity significantly.

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?

No guidance on when to use this tool versus siblings like get_all_equipment_categories_project or get_equipment_category. The description incorrectly suggests it fetches a specific record, providing misleading context. No when-not or alternative mentions.

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