get_item_info

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

No annotations are provided, and the description discloses no behavioral traits. There is no statement about side effects, return data, or operational context. The only added phrase, 'expanded operation', is vague and unexplained.

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 short but this is under-specification rather than helpful conciseness. It contains no front-loaded details, no structure, and every word is nearly a repetition of the tool name.

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?

With no annotations, no output schema, and an empty parameter schema, the description is the only source of context. It fails to explain what 'item' refers to, what info is retrieved, or how it relates to several similar sibling tools. The agent cannot reliably call or interpret this 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 schema lists zero named parameters but allow arbitrary properties via 'additionalProperties: true'. A baseline of 4 applies for zero documented parameters, but the description does not clarify whether any input is expected or what key might identify the item. The ambiguity prevents a perfect score.

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 is essentially a restatement of the tool name: 'get item info'. It does not specify what kind of item (project item, clip, sequence, etc.) or what information is returned. It also does not distinguish itself from closely named siblings like get_project_item_info or get_full_clip_info.

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?

There is no guidance on when to use this tool versus alternatives. The phrase 'expanded operation' gives no concrete selection criteria. No mention of prerequisites or common scenarios.

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