get-crm-v3-objects-objtype_objtype

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

No annotations are provided, and the description contains no behavioral information such as read-only status, pagination, response format, or error conditions. The single word 'List' offers no transparency beyond the operation's basic nature.

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?

Under-specification is not conciseness. A one-word description omits essential information and provides no value, earning a low score despite its brevity.

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's CRUD context, one parameter, and no annotations or output schema, the description is entirely inadequate. An agent cannot determine the tool's function, expected inputs, or return value.

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 schema fully documents the objectType parameter, but its description 'Path parameter objectType' is itself minimal. The tool description adds no information about acceptable values or how the parameter impacts the returned data, so it does not enhance the 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 is the single word 'List', which does not specify what is being listed or any distinguishing scope. It essentially restates the action implied by the tool name without adding resource details, making it impossible to differentiate from sibling listing tools.

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 such as get-crm-v3-objects-objtype-objid_objid or the v4 listing tool. The description lacks any context on suitable scenarios.

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