github_actions_add_selected_repo_to_org_secret

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

With no annotations, the description must convey behavioral traits. It only says 'Add', implying mutation, but does not disclose idempotency, required permissions, or whether the secret must already exist. This is a significant gap.

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 with no unnecessary words. However, it lacks structure; key information is not front-loaded and brevity comes at the cost of 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 description is too brief for the tool's context. It does not specify what happens if the repository is already selected, or that the secret must be an organization-level secret. No output schema exists, so more behavioral detail is needed.

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?

Although schema coverage is 100%, the parameter descriptions are merely the parameter names (e.g., 'org'), providing no additional meaning. The tool description does not elaborate on the parameters, leaving the agent without context on how to fill them.

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 action ('Add selected repository') and the target resource ('organization secret'), distinguishing it from sibling tools like 'github_actions_remove_selected_repo_from_org_secret'. However, it could be slightly more specific about what 'selected' means in this context.

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, such as 'github_actions_set_selected_repos_for_org_secret' or 'github_actions_list_selected_repos_for_org_secret'. No mention of prerequisites or conditions.

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