github_agent_tasks_get_task_by_id

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

No annotations are present, so the description carries the full burden. It simply states 'Get a task by ID' without disclosing any behavioral traits such as whether the task exists, required permissions, error conditions, or return format. The description adds minimal value beyond the name.

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 sentence, making it concise. However, it is overly brief and lacks detail that would be helpful for an agent, such as distinguishing from siblings or specifying the task's context. It earns its place but does not provide enough value.

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 absence of output schema and annotations, the description is incomplete. For a simple retrieval tool, it should at least mention the scope or common use cases. The presence of a sibling tool with a different signature means more context is needed to guide correct tool selection.

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 input schema has 100% coverage, with parameter 'task_id' described as 'task_id'. The description adds no additional meaning beyond what the schema already provides. Baseline 3 is appropriate since the schema already documents the parameter adequately.

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 'Get a task by ID' clearly states the action and resource. It is specific but does not differentiate from the sibling tool 'github_agent_tasks_get_task_by_repo_and_id', which also gets a task but with an additional repo identifier.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives like 'github_agent_tasks_get_task_by_repo_and_id' or 'github_agent_tasks_list_tasks'. An explicit note about the lack of filtering or alternatives would help.

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