composio_execute

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

With readOnlyHint and other annotations all false, the description carries the burden of disclosing behavior. It adds valuable detail: reads execute immediately, writes are only previewed for Telegram approval, and action_commit must not be called. It stops short of explaining the post-approval flow, but the core behavioral warning is present.

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?

The description is three short sentences with no filler. The purpose is front-loaded, and the critical warning about action_commit is placed last without diluting the main instruction.

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 two-parameter tool with no output schema, the description covers the execution mode, the argument source, and the approval/commit warning. Missing slug semantics and read return behavior are minor gaps but leave some ambiguity for an agent that lacks broader Composio context.

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?

Schema description coverage is 0%, so the description must compensate. It explains arguments_json as a JSON object matching input fields from composio_search, which is useful, but it does not explain slug beyond its name or how to obtain a valid slug. The compensation is incomplete.

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 states a clear verb and resource: run a Composio read now, or preview a write for Telegram approval. It also distinguishes itself from the sibling action_commit by explicitly saying never call action_commit, so the agent can tell its role apart from related tools.

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?

It gives actionable context: arguments_json should match fields from composio_search, writes return needs_approval, and action_commit should not be called. It does not fully spell out the complete search-then-execute flow, but the usage context is clear enough to route an agent correctly.

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