get-crm-v4-objects-objtype_objtype

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

With no annotations, the description must fully disclose behavior, but 'List' reveals nothing about return format, pagination, required permissions, or side effects. It adds no context beyond the tool name.

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 extremely short ('List') but under-specifies the tool's purpose and behavior. It is not concise in a useful way; it omits critical information, similar to the 'Process' calibration example.

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 has one parameter, no output schema, and no annotations, the description should provide essential context about what the tool does and returns. 'List' is completely inadequate for an agent to select and invoke the tool correctly.

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 100% (objectType is described as 'Path parameter objectType'), which meets the baseline. The description 'List' adds no semantic detail about how the parameter affects the operation, but the parameter is self-explanatory from its name and schema.

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 'List' is a verb but lacks a resource or scope. It does not state what is being listed, and the tool name suggests it lists CRM v4 objects by object type, but the description alone is too vague to distinguish from siblings like get-crm-v4-objects-objtype-objid_objid.

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 the many sibling tools (e.g., v3 object listing, single-object retrieval, batch operations). There is no mention of the objectType parameter or any alternative tools.

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