dashy_get_item

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

The readOnlyHint annotation already indicates a safe read operation. The description adds behavioral context by explaining that the item can be located by index or exact title, and the section by index or exact name. It does not disclose error handling, match case-sensitivity, or behavior when not found, but the annotation lowers the expected burden.

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, front-loaded sentence that efficiently conveys the action and the two addressing modes. No unnecessary words or repetition.

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?

The description adequately covers the core lookup behavior, and an output schema exists for return values. However, it omits the optional filename parameter and does not clarify whether index is zero-based or how to distinguish an index from a title. These gaps make it less than fully complete for a 3-parameter 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?

With 0% schema description coverage, the description compensates by explaining that iid is the item identifier (index or exact title) and sid is the section identifier (index or exact name). However, the optional 'filename' parameter is not mentioned, leaving its purpose unclear.

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 tool retrieves a single item within a section, and specifies that it can be found by index or exact title/name. This distinguishes it from sibling tools like list_items, get_section, or delete_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 implies usage for retrieving one specific item, but does not explicitly state when to use this over alternatives like dashy_list_items. No when-not-to-use or alternative tool is mentioned, leaving the guidance implicit.

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