List secrets in a company

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description adds authorization class ('board_or_agent'), which is helpful. However, it does not disclose other behavioral traits like rate limits, pagination, or what the secrets list contains.

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 concise (two sentences) and front-loaded with the purpose. The second sentence adds relevant operation and auth details without unnecessary fluff. A small improvement would be to merge the first sentence with the title repetition.

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?

The tool has an output schema, so return values need not be described. However, the description lacks parameter semantics and usage guidelines, making it barely adequate for the agent to correctly invoke the tool. The annotations compensate somewhat, but the description could be more helpful.

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 coverage is 0%, and the description does not explain the 'companyId' parameter beyond its implicit presence in the path. The agent receives no guidance on what companyId represents or how to determine its value.

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 title and description clearly state the tool lists secrets in a company. The description clarifies it's a GET operation to /api/companies/{companyId}/secrets. However, it does not specify what constitutes a 'secret' in this context, which leaves some ambiguity for the agent.

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?

The description provides no guidance on when to use this tool vs alternatives (e.g., creating or updating secrets, listing secrets for the current agent). No context or exclusions are given, forcing the agent to rely on 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.