Apply company import

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

Beyond the annotations (readOnlyHint false, destructiveHint false, idempotentHint false), the description adds minimal behavioral context. It mentions authorization but does not disclose side effects, idempotency, or limitations such as whether applying an import overwrites data or requires certain permissions beyond 'board_or_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 very short and front-loaded with the title. However, it sacrifices substance for brevity. While not verbose, it does not use its structure to convey necessary information effectively.

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?

Given the presence of an output schema, the description need not detail return values, but it fails to explain the tool's role in the import workflow (e.g., that it likely finalizes a previously previewed import). It lacks context on prerequisites, sequence, or relationships with sibling import tools.

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 input schema has two parameters (body and path.companyId) with 50% description coverage, but the tool description adds no information about their meaning, format, or how they affect the operation. The agent must rely solely on the schema, which is insufficient.

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 states 'Apply company import' and provides the HTTP method and path, which gives a basic idea of the action. However, it does not explain what 'apply' means in context or distinguish it from sibling tools like pc_post_companies_import or pc_post_companies_by_company_id_imports_preview.

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 usage guidance is provided. The description does not indicate when this tool should be used, what preconditions exist (e.g., a prior import preview), or when alternatives 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.