abx_get_action_secrets

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

Annotations already declare this as a read-only, idempotent, non-destructive GET. The description adds the organization-level scope and HTTP endpoint, but it does not explain return format, pagination, or whether secret values are returned or redacted.

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 short but redundant: 'Fetch all action secrets' and 'Retrieves all action secrets for given organization' restate the same purpose before repeating the endpoint. It is front-loaded but not maximally efficient.

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?

For a simple, parameterless list operation with rich safety annotations and no output schema, the description is adequate to invoke correctly. It leaves some context gaps around sensitive-data handling and response shape, but those are secondary for selection and invocation.

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?

There are zero parameters, so there is no parameter semantics to document. The baseline for a parameterless tool is 4.

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 states a specific verb and resource: fetch all action secrets for the organization. It is clear it is a bulk retrieval, but it does not name or distinguish against siblings such as abx_get_action_secrets_by_id or abx_post_action_secrets.

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?

It says it retrieves all action secrets, but gives no explicit when-to-use guidance, no exclusions, and no mention of alternatives like the by-id secret lookup or the create/delete secret tools.

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