github_dependabot_add_selected_repo_to_org_secret

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

With no annotations, the description bears full responsibility for behavioral disclosure. It indicates a mutation (adding a repo) but does not mention that the secret must already exist, whether the operation is idempotent, what happens on duplicate, or authentication needs. This leaves significant gaps for an agent.

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, which is concise but lacks structure and detail. It serves as a basic summary but does not front-load key information or organize content effectively.

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 no annotations, no output schema, and three required parameters, the description is too minimal to be contextually complete. It omits important details such as return values, prerequisites, and behavioral constraints, leaving an agent with insufficient information to use the tool correctly.

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 description coverage is 100%, the descriptions are tautological (just parameter names). The tool description does not add any meaning beyond what the schema provides, failing to clarify the format of 'repository_id' (e.g., numeric ID vs name) or other constraints.

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 resource (organization secret), matching the verb+resource pattern. However, it does not explicitly distinguish from similar tools like 'github_actions_add_selected_repo_to_org_secret' or 'github_codespaces_add_selected_repo_to_org_secret', relying on the tool name to convey the Dependabot 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?

No guidance is provided on when to use this tool vs alternatives such as 'github_dependabot_set_selected_repos_for_org_secret' (bulk update) or 'github_dependabot_remove_selected_repo_from_org_secret'. Prerequisites (e.g., secret must exist) are also omitted.

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