get_task

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

Beyond the annotations (openWorldHint=false, destructiveHint=false), the description reveals non-obvious behavior: get_task can be re-invoked to repeat the current task, its response carries an execution_instruction, and the agent is expected to loop back. This meaningfully helps the agent predict and act on the tool's behavior.

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 a single dense sentence that front-loads the core purpose and then packs the necessary behavioral workflow into the rest. Every clause adds information; there is no filler or restatement.

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?

For a zero-parameter tool with no output schema, the description is sufficient: it says what the tool does, what the agent should do with the returned task, and what to call next. The absence of detailed return-field documentation is acceptable because the execution_instruction is explicitly referenced.

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 tool has zero parameters and the schema fully covers this, so no parameter detail is needed. The description also reinforces the expected call shape by literally showing 'get_task {} again,' which is a small but useful confirmation.

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 states a clear verb-resource pair: it issues or repeats 'the one current security-review task.' It also distinguishes itself from sibling tools by framing get_task as the source of the task and the loop entry point, with report_done as follow-up.

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 explicitly explains the workflow: read source serially, submit report_done for coverage verification, then immediately call get_task {} again. This gives the agent concrete when-to-use-next guidance and names the sibling tool involved, leaving little to inference.

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