get_item

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

The description lacks any behavioral disclosure beyond 'Get' and 'Returns: The item'. It does not mention read-only nature (no annotations provided), authentication requirements, error handling, or side effects. An agent cannot infer safety or constraints.

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 and uses a clear Args/Returns format, but it is not front-loaded with essential context. Every sentence is present, but the overall brevity sacrifices necessary detail.

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 presence of many sibling tools and an output schema, the description does not explain how return values map to item types or provide context about error behavior. It fails to help an agent understand when this tool is the correct choice.

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 no description and the description only restates 'The fullname of the item', adding minimal value. With 0% schema description coverage, the description should clarify the parameter format (e.g., full path pattern) but fails to do so.

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 'Get specific item from Jenkins' which provides a verb and resource, distinguishing it from list-oriented siblings like get_all_items. However, the term 'item' is ambiguous given many get_* tools (e.g., get_build, get_view) and the description does not clarify what constitutes an item.

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 offers no guidance on when to use this tool versus alternatives such as get_all_items or query_items. It implies usage when you have a fullname, but does not explain prerequisites or scenarios where other tools would be more appropriate.

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