Get entities from Creatio

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

With no annotations provided, the description carries the full burden. It implies a read-only listing operation ('Return all...') but does not explicitly state behavioral traits such as read-only guarantee, idempotency, or any side effects. This is minimally adequate but leaves some uncertainty.

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?

Two sentences, front-loaded with the primary action. No filler words. Every sentence adds value: first defines the tool's purpose, second provides critical usage guidance.

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 simple listing tool with no parameters and no output schema, the description is reasonably complete. It explains what is returned (OData entity sets) and how to proceed. Lacking perhaps mention of the nature of the returned items (names/IDs), but sufficient for agent action.

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 description does not need to explain parameters. Baseline for 0 params is 4, and the description adds no additional parameter semantics (none are needed).

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 clearly states the tool returns all available Creatio OData entity sets, using the specific verb 'Return' and resource 'entity sets'. It distinguishes from siblings by positioning itself as the starting point before using 'describe-entity'.

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 provides explicit workflow guidance: 'Start here, then use describe-entity to inspect fields and keys before performing CRUD.' This gives clear context on when to use this tool relative to siblings, though it does not explicitly state when not to use it.

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