get_js_objects

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

Describes return content and filtering behavior but does not disclose side effects (e.g., read-only) or permissions. Without annotations, this is a moderate disclosure.

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 sentences front-load the core return content, then explain filtering. No unnecessary words.

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 one optional parameter and no output schema, description covers return structure and usage. Could mention errors or limits, but adequate for a simple read 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?

The only parameter, js_object_ids, is fully explained: passing a list filters, omitting returns all. The schema only provides its name and type, so the description adds significant meaning.

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 'Return the full source of JS objects' with specific fields (body, function body, variables, id/name/pageId). Distinguishes from sibling tools like list_js_objects and delete_js_objects.

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?

Provides explicit filtering guidance: pass a list of ids to filter, omit for all. However, no comparison with sibling tools like list_js_objects (which might return summary) or execute_js_functions.

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