creatio_list_allowed_entities

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

With no annotations, the description carries the full burden. It discloses an important behavioral nuance: if the allowlist is empty, all entities are readable. This adds context beyond a simple listing, though it does not describe the exact return format or pagination, which are minor for a metadata list.

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 two sentences, front-loaded with the primary purpose, and includes a one-sentence edge case. Every word adds value without redundancy. This is exemplary conciseness.

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?

Given low complexity, zero parameters, and no output schema, the description covers the core functionality and a key edge case. It is sufficient for an agent to understand what the tool does, though lacking an explicit mention of return structure is a minor gap.

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 tool has zero parameters, so the input schema provides complete coverage. The baseline for 0 params is 4, and the description does not need to compensate. It accurately reflects that no parameters are required.

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 'List' and identifies the resource 'Creatio OData entity sets' along with the context 'this server is permitted to read.' It clearly distinguishes from siblings like creatio_query_records and creatio_get_record, which focus on records rather than metadata discovery.

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 usage as a discovery step before querying or getting records, but it does not explicitly state when to use this tool versus alternatives or provide exclusions. The sibling names suggest a workflow, but the description itself lacks direct guidance.

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