get_csm_account

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe, read-only access. Description adds that the result includes contacts and open cases count, which is useful but does not provide deeper behavioral context like pagination, error conditions, or performance. With annotations covering safety, the description adds moderate value.

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?

Single sentence of 12 words that is front-loaded with action and resource. Every word is meaningful, no redundancy. Efficient and easy to scan.

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 read tool with one parameter and no output schema, the description provides adequate context about what is returned (contacts and open cases count). However, it could be more complete by briefly noting the response structure or example values. Overall, it is sufficient for the tool's complexity.

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?

Single parameter name_or_sysid is described in the schema with its meaning. The description does not add additional semantics (e.g., format, examples, or validation). Since schema coverage is 100%, this meets the baseline but does not enhance 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?

Description clearly states the tool retrieves account details with specific contents (contacts and open cases count). The verb 'Get' and resource 'customer account' are specific, and the description distinguishes from sibling list_csm_accounts which returns a list.

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 when-to-use or when-not-to-use guidance. The description implies retrieval of a single account, but does not contrast with sibling tools like list_csm_accounts or search_csm_accounts. Usage context is implied but not clearly delineated.

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