Get Equipment By ID (Company)

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint. The description adds that it returns a JSON object and mentions the endpoint, but does not disclose additional behavioral traits like pagination behavior (though schema hints via page/per_page) or any limitations. This is adequate but not rich.

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 about 5 sentences with some redundancy (e.g., 'Equipment records' repeated). It front-loads the purpose but could be more concise. Neither extremely efficient nor overly verbose.

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?

No output schema is provided; description mentions a JSON object but doesn't specify fields. Annotations cover safety. The description lacks details to help an agent choose between this and similar equipment retrieval tools (e.g., list_all_equipment_company). Adequate for basic use but incomplete in guiding selection.

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% with clear descriptions for all 4 parameters. The description simply lists required parameters without adding new meaning beyond what the schema provides. Baseline of 3 is appropriate.

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 clearly states the tool fetches full details of a specific Equipment record by ID at the company level. It specifies required parameters and the API endpoint. While it doesn't explicitly differentiate from sibling tools like 'get_equipment_by_id_project', the name and context make the purpose clear.

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 says to use it to fetch full details by identifier, but provides no guidance on when not to use it or alternatives. Siblings exist for project-level access, but no exclusions or alternative recommendations are given.

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