github_actions_list_repo_organization_secrets

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

No annotations; description does not disclose authentication requirements, pagination behavior (though schema defines it), or any side effects. Very little beyond the 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?

Single sentence, no waste, front-loaded. However, it is perhaps too brief for a tool with many siblings and parameters.

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?

Does not explain what 'repository organization secrets' means versus similar concepts, nor does it mention output format or pagination usage. Despite schema having those details, the description offers no context.

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?

Schema covers 100% of parameters with descriptions, but those descriptions are minimal (owner, repo) or external (per_page, page link). The tool description adds no additional meaning.

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 the action (list) and resource (repository organization secrets). It is specific and distinct from sibling names like 'list_org_secrets' or 'list_repo_secrets', but does not explicitly differentiate.

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 like github_actions_list_org_secrets or github_actions_list_repo_secrets. No context on appropriate scenarios.

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