Api composer data retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered and nothing is contradicted. However, the description adds no behavioral context at all - it never explains what 'api composer data' is, whether auth is required, or what openWorldHint implies for this call.

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 short, but the single token is a verbatim echo of the identifier rather than an informative sentence, so no sentence earns its place and nothing is front-loaded.

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 descriptive text, an agent has no way to know what data this returns or when to call it. For an opaque retrieve endpoint the description needs to carry the full burden and carries none of it.

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 defines zero properties, so there are no parameters whose semantics could be clarified and the baseline of 4 applies. The description neither adds nor detracts from parameter meaning.

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 literally the tool name with underscores swapped for spaces: "api_composer_data_retrieve". It states no verb, no resource, and no scope, and with hundreds of sibling ciso_assistant_api_* retrieve tools an agent gains zero ability to distinguish this endpoint.

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, when-not-to-use, or alternative-naming guidance. Nothing tells the agent which task or entity type routes here instead of ciso_assistant_api_composer... siblings or the many other *_retrieve endpoints.

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