get_frame_callees

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description is not required to restate safety. It adds context about 'bounded' and 'direct' callees, but does not explain cursor-based pagination or how 'source-linked' is resolved. This is acceptable but not extensive.

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?

A single, concise sentence front-loads the core action and key qualifiers. No redundant phrases or filler.

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 is sufficient for a simple read-only query tool: output schema covers return structure, annotations cover safety, and the description conveys the essential scope. It could mention pagination or contrast with get_frame_callers, but the omissions are not critical given the schema and sibling context.

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 covers three of four parameters with descriptions (limit, frame_id, run_or_artifact), leaving cursor undocumented. The tool description mentions 'bounded', which aligns with limit, but adds no extra meaning for cursor or other parameters. With 75% schema coverage, the description is not a major additional source of parameter semantics.

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 identifies the tool's action: 'Return bounded source-linked direct callees for a frame.' It specifies a distinct resource (callees vs. callers) and includes qualifiers (bounded, direct) that differentiate it from sibling tools like get_frame_callers.

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, such as get_frame_callers for the opposite relationship. The description also omits prerequisites like needing a frame_id from an analysis result, even though that is mentioned in the schema.

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