infoset_get_company

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

No annotations are available, so the description carries the full burden. It only states the basic action without disclosing return format, potential errors, authentication requirements, or side effects. The read-only nature is implied by the name but not confirmed by annotations or description.

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 a single concise sentence that directly conveys the tool's purpose without any fluff or redundancy. Every word earns its place, making it highly efficient.

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?

For a simple get-by-id tool, the description is minimally adequate: it states the action and the parameter. However, it lacks contextual detail about return values or behavior, and the absence of annotations makes it insufficient for full autonomy. It does not address alternatives like batch_get_companies, but that is more a usage guideline concern.

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 schema already describes the only parameter, companyId, as 'Company ID' with 100% coverage. The description simply repeats this concept without adding constraints, examples, or format details, meeting the baseline for high schema 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 clearly states the action 'Get company information' and specifies the identifier 'by company ID'. This distinguishes it from sibling get tools like infoset_get_ticket and infoset_get_contact, making the purpose unambiguous.

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 is provided on when to use this tool versus alternatives such as infoset_batch_get_companies. There is no mention of prerequisites, exclusions, or contexts where another tool would be more appropriate.

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