get_sources_at_frame

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

No annotations provided; description says 'get source nodes visible at a specific frame' but lacks details on side effects, performance, or what 'visible' entails. Carries full burden but is minimal.

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?

Two short sentences, no redundant info, front-loaded with purpose. Every word earns its place.

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?

Has output schema, so return details not needed. Lacks differentiation from 'get_sources', but for a simple query tool, description is functionally complete.

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?

Schema coverage is 0%, but description explains 'frame' parameter meaning and special value -1 for current frame, adding useful context beyond the schema.

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?

Clearly states 'Get source nodes' (verb+resource) and 'visible at a specific frame' (scope), which distinguishes it from sibling 'get_sources' that likely returns all sources.

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?

Implies usage when you need sources at a particular frame, but does not explicitly mention when not to use or list alternatives like 'get_sources'.

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