get_project_item_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states only 'expanded operation' and does not mention whether the operation is read-only, what data it returns, or any side effects, leaving the agent completely uninformed.

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 short, but the opening 'Premiere Pro expanded operation:' is filler that does not add value. It is concise in word count but not in meaningful content, making it minimally acceptable rather than well-structured.

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?

Without an output schema or annotations, the description needs to explain what information is returned and how this 'expanded' version compares to get_item_info. It does neither, leaving the tool under-specified for reliable agent use.

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 tool has zero defined parameters and 100% schema coverage, so the schema already accounts for the input structure. With no parameters to explain, the description is not required to add parameter-level semantics, and the baseline of 4 applies.

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 states the tool gets project item info, matching the name, but the phrase 'expanded operation' is vague and doesn't clarify what 'expanded' means or how this tool differs from the sibling get_item_info. It names a verb and resource but lacks specificity.

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 is provided about when to use this tool versus alternatives like get_item_info, list_project_items, or get_item_info. There is no context, prerequisite, or exclusion information, so an agent cannot determine when this tool is the appropriate choice.

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