get-crm-v3-object-library-enablement_enablement

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

With no annotations and no behavioral disclosure, the description is completely opaque. It doesn't state whether pagination, filtering, or rate limits apply, nor what the output format is. The phrase 'Read All' is the only behavioral hint, and even that is ambiguous.

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 only two words, but this is under-specification rather than effective conciseness. It lacks any structure or detail needed for comprehension, similar to 'Process' in the calibration examples.

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 the tool name suggests a specific resource (object library enablement), the description provides no context about the scope of 'All', what is returned, or any associated caveats. Without an output schema, the description should explain the return value, but it does not.

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 there is no parameter semantics to explain. Per the guideline, 0 params = baseline 4. The description doesn't need to add parameter meaning, and the schema is already complete with an empty properties object.

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 'Read All' uses a verb but the resource is unspecified; it doesn't mention 'object library enablement' or any specific entity. It fails to distinguish from sibling tools like get-crm-v3-object-library-enablement-var_var, which reads a single enablement.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent without direction on tool selection.

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