Get All Equipment Models (Company)

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that the response is a paginated JSON array with metadata, but discloses no additional behavioral traits beyond what annotations provide. No contradictions found.

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 (5 sentences) but contains an internal contradiction (get all vs. specific). The front-loaded purpose is clear, but the confusing second sentence detracts from overall conciseness.

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 tool lacks an output schema, so the description should compensate by detailing return fields. It only mentions 'paginated JSON array of Equipment records' without field specifics. The contradictory statement about fetching a specific record adds confusion, leaving the agent without a complete understanding.

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 baseline is 3. The description adds context for pagination parameters (page and per_page) by stating they control pagination, but does not elaborate on filter parameters (filters__is_active, filters__make_id) beyond what the schema provides.

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 first sentence clearly states 'Get all equipment models (Company)', but the second sentence contradicts it by saying 'fetch the full details of a specific Equipment records by its identifier.' This inconsistency muddles the purpose. The distinction from siblings like 'get_all_equipment_models_project' is implied by the title but not explicitly stated in the description.

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 mentions required parameters and hints at pagination usage, but provides no guidance on when to use this tool versus alternatives (e.g., 'list_all_equipment_models' or 'show_equipment_model'). There is no explicit when-not-to-use or comparison with sibling tools.

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