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

No annotations are provided, so the description carries the full burden for behavioral transparency. While the description says 'Returns' which implies a read operation, it does not explicitly state that the tool has no side effects or that it is safe to call repeatedly. This is a minor gap for a get-style tool.

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 somewhat verbose with redundant phrasing ('use it both to check progress and to read the result' vs. 'Call it again when the user asks about progress') and includes an unnecessary note about profile_url formatting. However, it remains reasonably concise and well-structured.

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?

There is no output schema, but the description lists the fields returned (status, title, desc, budget, deadline, timeline, created, modified, specialist_invited, specialist_accepted, files). It also clarifies how to present profile_url and files. It doesn't address errors or edge cases, but for a simple fetch operation the given details are sufficient.

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 schema has one parameter, task_id, but the description does not explain its format, purpose, or constraints. Although the name is self-explanatory, the description adds no additional meaning beyond the type string. With 0% schema coverage, the description should have provided more context.

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 'Returns the whole task record' and distinguishes it from sibling tools like create_task, cancel_task, and search_specialists. It also explains its dual use for progress checking and result reading.

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 says when to use the tool ('use it both to check progress and to read the result') and repeats this guidance ('Call it again when the user asks about progress'). It does not mention alternative tools, but the context is clear.

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