github_repos_list_deployment_statuses

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

No annotations are provided, so the description carries full burden. It only states 'List deployment statuses' without mentioning pagination (page/per_page parameters), read-only behavior, or any side effects. The description is too minimal to inform the agent about important behavioral traits.

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 concise (3 words) and front-loaded, but it is too brief to be considered well-structured. While it avoids unnecessary text, it sacrifices clarity and completeness.

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?

The tool has 5 parameters, no output schema, and lacks annotations. The description does not explain that it returns an array of deployment status objects or that it requires a deployment_id. It leaves the agent with significant gaps in understanding the tool's full behavior.

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 description coverage is 100%, so the parameters are already well-documented. The description adds no extra meaning beyond what the schema provides. Baseline 3 is appropriate.

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 'List deployment statuses' clearly states the verb 'List' and the resource 'deployment statuses'. It implies listing multiple statuses, distinguishing it from 'get_deployment_status' which retrieves a single status. However, it does not explicitly mention that statuses are listed for a specific deployment (deployment_id is required in schema but not in description).

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 provides no guidance on when to use this tool versus alternatives like 'github_repos_get_deployment_status' or 'github_repos_list_deployments'. Given the large number of sibling tools, clear usage context is essential but missing.

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