submit_temp_site_task

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

No annotations provided; description carries full burden but only states basic function. No disclosure of side effects, blocking behavior, permissions, or other behavioral traits. Minimal information for an agent to understand implications.

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?

Description is very short with no wasted words. However, it could be better structured with separate sections for purpose, parameters, and returns. Effective use of docstring format.

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 zero annotations, one parameter with no schema description, and no output schema, the description is incomplete. It lacks details on task_data format, error cases, and integration context with sibling tools.

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 has 0% description coverage for the single parameter 'task_data'. Description adds 'including site, map, and area information', which provides some context but is vague and insufficient to convey structure or constraints.

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?

Description clearly states verb 'submits', resource 'temporary task', and context 'S-line robots with site information'. Slightly distinguishes from sibling 'submit_temp_no_site_task' by mentioning site info, but could be more specific about the task's nature.

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 on when to use this tool versus siblings like 'execute_s_line_site_task_workflow' or 'submit_temp_no_site_task'. Missing prerequisites or context for selection.

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