getCallByCommId

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

The description only states the operation (Get) without disclosing behavioral traits like permissions, side effects, or data shape. Since no annotations exist, the description carries the burden, but it adds no extra transparency beyond the obvious read operation.

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, front-loaded sentence with no extraneous words. It efficiently conveys the tool's purpose.

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?

For a simple getter with one parameter and no output schema, the description is mostly adequate. It could mention what the returned record contains, but the current text suffices for understanding the tool's basic function.

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 coverage is 100% for the single parameter, which is described as 'Communication record ID' in the schema. The tool description reinforces that the ID identifies a call communication record, adding context beyond the schema's minimal description.

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 clearly states it gets a call communication record by its communication ID. The verb 'Get' and resource 'call communication record' are specific, and the suffix '(v2)' distinguishes it from potential v1 counterparts. It differentiates from siblings like getCallRecord or listCalls.

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 explicit guidance on when to use this tool versus alternatives like getCallRecord or listCalls. The implied use case is when you have a communicationId, but no when-not-to-use or alternative recommendations are provided.

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