Api chat agent actions reject create

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true; the description adds nothing about what state the rejection produces, whether it is reversible, or what permissions are needed. Without annotations an agent would learn nothing from this text.

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 that brevity is under-specification rather than economy: a single identifier string with no front-loaded statement of purpose, effect, or scope.

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 write tool with an openWorld hint, no output schema, and an undocumented required id, the definition gives an agent nothing to decide or act on. The name alone is not sufficient context to call this correctly.

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?

There is one required parameter, 'id', with 0% schema description coverage, so the description carries full responsibility for explaining it. It supplies nothing — it does not say whether 'id' identifies the action, the agent run, or the chat session.

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 raw slug 'api_chat_agent_actions_reject_create' repeated verbatim, which only indirectly signals a reject operation on a chat agent action. It restates the name and title rather than stating in prose what the tool does or what a 'reject' means here.

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 when-to-use guidance is given. Sibling tools such as ciso_assistant_api_chat_agent_actions_approve_create, _list, _retrieve, and _object_retrieve exist and are the obvious alternatives, yet none are distinguished or referenced.

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