Api findings assessments xlsx retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered without the description. The description adds no behavioral context of its own — nothing about whether the response is a binary file stream, how the id scopes the export, or whether the export reflects current or published state.

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 identifier token with zero sentences of content. This is under-specification rather than conciseness — there is no front-loaded purpose statement for anything to be trimmed from.

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 and an opaque id parameter, the description should at minimum state that the call returns an XLSX workbook of findings assessments and what the id selects. None of that is present, so an agent cannot confidently invoke it over its csv/pdf/md siblings.

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 single required parameter "id" has 0% schema description coverage, so the description must explain what kind of identifier it is and what entity it refers to. It says nothing, leaving the agent to infer that it is the findings-assessment id.

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 is the tool's slug restated verbatim ("api_findings_assessments_xlsx_retrieve") with no expansion into a verb+resource statement. An agent can guess it retrieves an XLSX export of findings assessments, but that inference comes from the name, not the description, and it does not distinguish this from siblings such as findings_assessments_pdf_retrieve or findings_assessments_md_retrieve.

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?

There is no guidance on when to use this tool versus the many other findings-assessment retrieval tools (retrieve, object_retrieve, list, csv/pdf/md exports). No exclusions, prerequisites, or alternative-selection criteria are provided.

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