Show Company Insurance

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

The description states the operation is read-only and returns a JSON object, aligning with annotations. However, it fails to explain the pagination parameters (page, per_page) in the schema, which are atypical for a show endpoint and could confuse an agent.

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 (3 sentences plus API info) and front-loaded with purpose. Every sentence adds value, with no wasted words.

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 lacks explanation of the response structure (e.g., fields returned) and does not address the presence of pagination parameters for a single-record fetch. Given the tool's simplicity and annotations, it is adequate but not fully complete.

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 description only lists required parameters (company_id, id) without adding meaning beyond the input schema. Since schema coverage is 100%, the baseline is 3, and the description does not improve upon it.

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 verb 'Return' and resource 'Insurance/Directory records', and distinguishes itself as a single-record fetch by mentioning 'specific' and 'by its identifier'. It also provides the API endpoint, reinforcing its purpose.

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 says 'Use this to fetch the full details of a specific Directory records by its identifier', giving clear when-to-use guidance. However, it does not explicitly mention when not to use this tool (e.g., for listing multiple records) or point to alternative tools like list_company_insurances.

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