isw_get_customer_demographics

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

With no annotations provided, the description carries the full burden. It only says 'Get', implying a read operation, but fails to disclose any behavioral traits such as required permissions, response size, rate limits, or consequences of invalid inputs.

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 extremely concise (4 words) but at the cost of completeness. It lacks essential information that could be added without much verbosity. Effective conciseness would require including parameter hints or behavioral context.

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 absence of output schema, annotations, and schema descriptions, the description is severely incomplete. It does not explain the output format (what demographic fields are returned), the input requirements, or any error conditions. The agent has insufficient information to use the tool 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 input schema has two parameters (customerId required, extra optional) with 0% schema description coverage. The description does not mention either parameter, providing no additional meaning beyond the schema. The agent cannot infer how to provide the customer identifier or what extra object might accept.

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 the verb 'Get' and the resource 'customer demographic profile'. While it lacks specificity on what demographics are included, it is distinct from sibling tool names which focus on transactions, cards, payments, etc.

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 on when to use this tool versus alternatives. There is no mention of prerequisites, typical use cases, or when not to use it. The description is silent on context.

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