get-crm-v3-properties-objtype_objtype

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. 'Read all properties' only states the action; it doesn't disclose return format, pagination, or that it returns property definitions rather than object values.

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 a single, concise sentence front-loaded with the verb 'Read'. It is efficient but slightly under-specified for a tool with 3 parameters.

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?

This is a simple list tool with no output schema and no annotations. The description is insufficient: it doesn't mention the required objectType scope, what 'properties' means (property definitions vs object values), or any response details. Given the available sibling tools, more context would help an agent select it 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?

The schema provides 100% coverage with descriptions for all three parameters (archived, objectType, properties). The tool description adds no additional parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 properties' clearly identifies the action (read) and resource (all properties), distinguishing it from siblings like get-crm-v3-properties-objtype-var_var which reads a single property. However, it doesn't explicitly state that properties are scoped to a given object type, relying on the tool name and schema.

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 usage guidance is provided. The description doesn't mention when to use this tool vs alternatives like post-crm-v3-properties-objtype_objtype or get-crm-v3-properties-objtype-var_var, nor any preconditions.

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