Api contracts export xlsx retrieve

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

The description says contracts can be 'viewed or edited', implying a write capability, while annotations declare readOnlyHint=true and destructiveHint=false — a direct conflict. The description also fails to convey that this is a file-export endpoint returning a binary XLSX payload, a behavior the annotations do not cover.

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?

It is a single short sentence with no padding, so it is structurally tight. However, the sentence spends its only clause on generic CRUD language rather than the export-to-XLSX behavior, so brevity buys no value here.

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?

With no output schema, no parameters, and no filter documentation, the description is the sole source of information about what an agent will receive — yet it never says the response is an XLSX file, what rows/fields it contains, or what scope of contracts is exported. That is a substantive gap for an export tool.

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 tool takes no parameters, so the schema carries no semantics burden and the baseline of 4 applies. The description adds nothing and nothing is missing in this dimension.

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 'API endpoint that allows contracts to be viewed or edited' is generic auto-generated CRUD boilerplate that never mentions the actual operation named in the tool: exporting contracts to XLSX. It does not distinguish this tool from the many siblings (contracts_list, contracts_retrieve, contracts_export_csv_retrieve), leaving the agent unable to tell what it produces.

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 indication of when to use this versus contracts_list, contracts_retrieve, or contracts_export_csv_retrieve, and no prerequisites or exclusions are stated. The agent gets no routing signal at all, so a name-only guess is the only recourse.

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