github_dependabot_list_org_secrets

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

The description omits behavioral traits such as pagination (though the schema includes `per_page` and `page`), read-only nature, or any potential side effects. With no annotations, the description should disclose that this is a safe read operation and how results are delivered. It fails to do so.

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 extremely concise at one sentence, but it sacrifices informativeness. It is not front-loaded with critical details like scope or output, making it less useful despite its brevity.

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?

With 3 parameters and no output schema, the description should explain what the tool returns (e.g., a list of secrets) and any important context. It does not, leaving the agent to guess the return value and behavior.

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% description coverage, so each parameter's purpose is already documented. The description adds no additional meaning beyond the schema, earning a baseline score of 3.

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 'List organization secrets' clearly states the action (list) and resource (organization secrets), making the purpose immediately understandable. However, it does not explicitly distinguish it from sibling tools like `github_dependabot_get_org_secret`, though the verb 'list' vs 'get' implies the difference.

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. For example, it does not mention that this lists all secrets for an organization, while `github_dependabot_get_org_secret` retrieves a single secret. The agent must infer usage from sibling tool names alone.

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