github_codespaces_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 disclose behavioral traits. It only states the action ('Add') but doesn't clarify idempotency, required permissions, error handling, or side effects. This is insufficient for a mutation tool.

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 fluff. However, the extreme brevity sacrifices useful details that could be included without harming conciseness.

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 and no output schema, the description should cover more context: return value, error cases, and relationship to other codespaces secret tools. It only covers the basic action, leaving significant gaps.

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 but the descriptions are just the parameter names (e.g., 'org', 'secret_name', 'repository_id'), offering no additional meaning. The tool description adds no extra parameter context, so it meets the baseline for high schema coverage.

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 'Add selected repository to an organization secret' clearly states the action (add), the resource (repository), and the target (organization secret). This sufficiently distinguishes it from user-level tools, though it doesn't differentiate from other similar add tools like 'github_actions_add_selected_repo_to_org_secret' or 'github_codespaces_set_selected_repos_for_org_secret'.

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 versus alternatives, prerequisites (e.g., the secret must exist), or scenarios to avoid. The description lacks any explicit usage context or exclusions.

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