github_actions_update_hosted_runner_for_org

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Update' without clarifying that this is a write operation, potential side effects, authorization needs, or rate limits. The body parameter is described only as 'Request body (JSON object)', lacking constraints or examples.

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, front-loaded sentence with no extraneous words. It is appropriately concise for a tool with a self-explanatory name and schema.

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 tool's nature (an update mutation with a free-form body), the description is incomplete. It lacks information on return values (no output schema), expected body structure, and any behavioral notes. Sibling tools for create and delete likely have richer descriptions, leaving this one under-specified.

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%, but the description itself adds no extra meaning to the parameters. It does not explain what 'hosted_runner_id' refers to or suggest valid properties for the body. The baseline of 3 is lowered because the description provides zero supplementary information beyond the schema's minimal labels.

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 verb 'Update' and the resource 'GitHub-hosted runner for an organization', which distinguishes it from sibling tools like create, delete, get, and list. However, it omits what specific aspects can be updated, which is partly addressed by the input schema's body parameter.

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 (e.g., when to update vs. create or delete). No prerequisites or context for usage are mentioned, leaving the agent to infer from the name alone.

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