task.status

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

No annotations are provided, so the description must cover behavioral traits like idempotency, side effects, or prerequisites. The description only states 'Get task status' — it does not disclose whether the task refers to a long-running process, if it returns immediately or requires polling, or if it has rate limits. This is insufficient for safe tool invocation.

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 extremely short at 3 words, which is concise but verging on under-informative. It wastes no words, but for such a brief description, the front-loading attribute is irrelevant. It earns points for brevity but loses a point for sacrificing clarity, as the tool name already implies the description.

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 the complexity of the system (many sibling tools involving tasks, analysis, sessions), this description is too minimal. There is no output schema, no mention of return values (e.g., string status, JSON object), and no context about what 'status' means (e.g., pending, running, completed). The agent cannot know how to use the response.

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% (the parameter 'task_id' has no description in the schema), so the description must compensate. Task_id is self-explanatory as it is a common identifier, but the description adds no additional context like expected format, source (e.g., from a previous tool call), or validation rules. Baseline is 3 due to only one parameter, but added value is minimal.

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 verb 'get' clearly indicates a read operation, and 'task status' specifies the resource. However, given the context of sibling tools from a binary analysis platform, it competes with tools like 'task.analysis_update' and 'task.result', and the description does not distinguish itself from these. Still, it communicates a straightforward purpose.

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 on when to use this tool vs alternatives. Sibling tools like 'task.search_text', 'task.result', and 'task.cancel' suggest there are multiple task-related operations, but the description offers no criteria for selecting this one, leaving the agent without decision support.

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