secrets_get_acl

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

The annotation readOnlyHint=true already marks this as a read operation. The description 'Fetch' is consistent and adds no contradictory information. However, it does not disclose additional behavioral aspects such as error handling (e.g., if principal has no ACL) or authentication requirements. Given the annotation, the description is adequate but not enriched.

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 that immediately conveys the action and resource. No extraneous text. It is well front-loaded and to the point.

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 fetch operation with a known output schema, the description is sufficient. It identifies the two required parameters (scope and principal) and the action. No critical gaps given the availability of the output schema and annotations.

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 description coverage is 100%: both parameters have clear descriptions ('Scope name', 'Principal name') in the schema. The tool description adds minimal semantic value by tying 'principal' to the ACL, but does not explain format or constraints beyond the schema. Baseline is 3 since coverage is high.

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 uses a specific verb 'Fetch the ACL' on a specific resource ('secret scope' for a 'principal'), clearly distinguishing it from siblings like secrets_list_acls (which lists all ACLs on a scope) and secrets_get_secret (which gets a secret value).

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 explicit when-to-use or when-not-to-use guidance is provided. However, the name and context imply usage: use this tool to fetch a single ACL for a specific principal, while secrets_list_acls would be used to list all ACLs on a scope. The guidance is implied but not stated.

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