cigchat_get_integration_dropi

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

With no annotations, the description carries the transparency burden. It discloses the HTTP method (GET), endpoint path, and authorization scope requirement. It does not explicitly state that the operation is side-effect-free or describe the response shape, but the GET semantics and 'get config' phrasing provide reasonable behavioral clarity.

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 a single, front-loaded sentence that states purpose, endpoint, and scope requirement. Every element carries useful information, with no redundancy or 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 config retrieval tool with no output schema, the description provides the essential context: what is retrieved, the endpoint, and required permissions. It could mention the return format, but that is not critical for such a simple read operation.

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 has zero parameters, so the baseline is 4. There are no parameter semantics to add, and the description doesn't need to compensate for any schema gap.

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 uses a specific verb+resource construction: 'Get the config of Dropi integration', and reinforces it with the HTTP endpoint [GET /integration/dropi]. This clearly distinguishes it from sibling integration tools like set/clear or get_integration_* for other services.

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?

The description implies the appropriate use case through 'Get' and explicitly states the required 'Manage Team' scope on the token, giving clear operational context. It does not explicitly contrast with set/clear integration alternatives, but the read-only verb and endpoint make the intended usage obvious.

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