Get Item Children

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

No annotations are provided, so the description carries the burden. It discloses the types of children returned (attachments, notes) and that attachments include PDFs, snapshots, linked files, adding behavioral context. However, it does not mention edge cases (e.g., empty results, invalid itemKey), pagination, or what the note format contains, leaving some behavioral details unclear.

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 concise, front-loaded with the main action, and uses bullet points for clarity. Each sentence earns its place: it defines the tool, enumerates child types, and gives a follow-up usage instruction. No fluff or redundant phrasing.

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 a single-parameter tool with no output schema, the description provides sufficient context about what the tool returns (attachment types and note existence) and a next step (using download_attachment). However, it lacks details about the structure of notes or how to handle attachments beyond the key, leaving some gaps for a fully self-contained description.

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 covers the only parameter 'itemKey' with a description ('The key of the parent item'), so schema coverage is 100%. The description does not add extra semantics beyond what the schema provides; it simply reiterates that it is a parent item. Per the rubric, the baseline for 100% coverage is 3.

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 explicitly states it gets child items (attachments, notes) of a parent item, with a clear verb and resource. It enumerates attachment types (PDF files, snapshots, linked files) and distinguishes from the main item, making it specific and differentiating from sibling tools like get_item. The reference to download_attachment further clarifies its role.

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 context: use it to fetch child items and then use the attachment key with download_attachment. However, it does not explicitly state when to use this tool versus alternatives like get_item or search_items, nor does it provide exclusions or when-not-to-use guidance. The guidance is present but not fully explicit.

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