github_codespaces_delete_org_secret

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

No annotations provided; the description merely restates the action without disclosing side effects, permissions required, or error conditions. The bare statement 'Delete an organization secret' adds no value beyond the tool name.

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?

Extremely concise (4 words), but appropriate given the simple delete operation. No structural elements (e.g., sections) needed.

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?

Lacks context to distinguish from sibling tools (e.g., github_actions_delete_org_secret). Does not clarify that this is specific to Codespaces.

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?

Input schema covers 100% of parameters but with minimal descriptions ('org', 'secret_name'). The tool description adds no further meaning, meeting 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?

Description clearly states verb 'Delete' and resource 'organization secret'. However, it does not differentiate from similar delete tools for other services (e.g., Actions, Dependabot) in the same server.

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 on when to use this tool versus alternatives (e.g., github_actions_delete_org_secret). Lacks context for appropriate usage.

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