dw_itemtype_get

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

With no annotations, the description relies on the word 'Get' to indicate a read operation, but it does not confirm lack of side effects or disclose any behavioral traits such as authentication requirements or rate limits. It adds context about restrictions but leaves other behaviors implicit.

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, efficient sentence that front-loads the purpose. Every word contributes meaning, with no superfluous information.

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 simple one-parameter input and no output schema, the description is relatively complete. It specifies the identifier and what is included (restrictions). It could mention the return format or that the systemName is case-sensitive, but the context is sufficiently covered for a straightforward retrieval tool.

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 100% coverage with a description for the systemName parameter. The description adds no additional meaning beyond the schema, so it meets the baseline. The parameter semantics are adequately handled by the schema.

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 action (Get), the resource (DynamicWeb item type), the identifier (by systemName), and includes context (including all restrictions). This distinguishes it from sibling tools like dw_itemtype_list which retrieves multiple items.

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?

The description implies usage when you have a specific systemName, but it does not explicitly state when to use this tool versus alternatives like dw_itemtype_list or when not to use it. No guidance on prerequisites or context is provided.

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