Export company data

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

The description adds the authorization class and endpoint details, providing some context beyond the annotations (readOnlyHint false, destructiveHint false). However, it does not disclose key behavioral traits like whether the export is synchronous or asynchronous, or what the output is, limiting transparency.

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, but the first sentence redundantly repeats the title. It is otherwise well-structured with the purpose front-loaded, and every sentence adds some information (endpoint and auth class). Could be improved by removing the duplicate.

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 complexity (2 params, nested objects) and the presence of sibling tools like exports_preview, the description lacks important context: it does not explain what the export produces, whether it is a file or job, or how it relates to the preview tool. The presence of an output schema is not leveraged.

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 body parameter has a description explaining it is optional and lacks a schema, which adds value. However, the required companyId parameter is undocumented in both the schema and description, so the description only partially compensates for the 50% 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 verb 'Export' and the resource 'company data', providing a clear purpose. However, it does not differentiate from the sibling tool pc_post_companies_by_company_id_exports_preview, so it loses a point for lacking sibling differentiation.

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 provides no guidance on when to use this tool vs alternatives like preview or import tools. It only gives technical details (HTTP method, path, authorization class) but no contextual usage advice.

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