Api entities export ecosystem retrieve

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so safety is covered. The description adds the useful fact that the output is a multi-sheet Excel workbook with exactly three sheets, which is behavioral context not present in the annotations. It says nothing about permissions/role requirements for exporting the TPRM ecosystem, which is the remaining gap.

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?

A single sentence that front-loads the verb and resource and packs the only two extra facts (Excel format, three sheets) without filler.

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 zero-parameter export with no output schema, the description conveys format and sheet count, which is adequate to invoke it. It does not say what the three sheets contain or how this report relates to the sibling entity export endpoints, so an agent choosing among the export family could still pick wrong.

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 zero parameters, so the schema has nothing to document and the description does not need to explain any inputs. That is the baseline-4 case; the description correctly does not waste words on parameters.

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?

States a specific verb (export), a specific resource (the TPRM ecosystem) and the output artifact (multi-sheet Excel with three sheets), which an agent can tell apart from the general entities export siblings. It stops short of naming the closest siblings (entities_export_xlsx_retrieve, entities_export_csv_retrieve), so the differentiation is inferred from 'ecosystem' rather than stated.

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 when-to-use or when-not-to-use guidance and no mention of the alternative export endpoints (entities_export_xlsx_retrieve, entities_export_csv_retrieve, analytics_export_xlsx_retrieve). The agent must guess whether the ecosystem report or the generic xlsx export is the right call.

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