post-crm-v3-properties-objtype-batch-read_read

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

With no annotations, the description must clarify safety and side effects. It does say 'Read', implying read-only, but it fails to disclose required fields (objectType, archived) or explain the structure of the body. The example contradicts the input schema, creating behavioral uncertainty.

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?

Though brief, the description's example is inaccurate and takes up space without conveying correct usage. The first sentence is clear but the rest is misleading, so the conciseness is not effective.

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?

Without annotations or an output schema, and with a confusing input schema, the description is far from complete. It does not explain what a 'batch of properties' means, how the response is structured, or how objectType and archived factor in. The tool is essentially unusable as documented.

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 description adds no meaningful semantics beyond the schema's generic descriptions. The example introduces 'properties' and 'propertiesWithHistory' fields that are absent from the schema, while the schema's 'inputs' is described as an array of property names only. This actively confuses parameter understanding.

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 says 'Read a batch of properties' but the example uses object IDs and properties to retrieve, which matches the sibling tool 'post-crm-v3-objects-objtype-batch-read_read' rather than a property-definition read. This ambiguity makes it unclear whether the tool reads property definitions or property values, and it fails to distinguish from closely related sibling 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 given on when to use this tool versus alternatives like the object batch-read tool. The example actually points to a different tool's usage (object IDs and property values), misleading the agent about the appropriate context.

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