sp_get_task

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

No annotations are provided, so the description carries full responsibility. It implies a read operation but doesn't explicitly mention that it doesn't modify anything. It also doesn't describe what happens if the id is invalid, but for a simple getter, the behavior is fairly obvious.

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, concise sentence that is front-loaded with the verb and resource. No fluff, easy to parse.

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 simple get-by-id tool with one fully documented parameter and no output schema, the description is adequate. It doesn't explain return values, but since the output schema is absent and it's a standard getter, this is not critical. However, it doesn't mention error behavior or edge cases, which might be useful.

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 parameter 'id' is fully described in the schema as 'Task id', and the description says 'by its id', so there is high redundancy. The schema already carries the meaning, and the description adds little beyond confirming the id is used for lookup.

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 clearly states the tool gets a single task by its id, which is specific and matches the name. However, it does not differentiate from other retrieval tools like sp_get_current_task or sp_list_tasks, though the phrase 'by its id' helps distinguish from list operations.

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 implies usage for retrieving a single task when you have its id, but it does not explicitly state when to use this over alternatives like sp_get_current_task or sp_list_tasks. There is no mention of when not to use it, but the context is clear enough for a simple get-by-id tool.

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