List my user secret values

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the authorization class ('board') and HTTP method (GET), which are useful but not deeply behavioral. It does not discuss side effects, rate limits, or what happens if no secrets exist.

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 (two sentences) but repeats the title in the first sentence. It is concise but could be more efficient by combining or adding unique information. The structure is simple and front-loaded.

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?

Given the sensitivity of secrets and the existence of an output schema (not shown here), the description lacks context about what the output contains or how to interpret results. The need for companyId is not explained. The 'board' authorization is mentioned without elaboration.

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 single parameter path.companyId has no description in the schema (0% coverage) and is not explained in the tool description. The agent must infer that a company ID is required from the path template. No guidance on format or 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?

The description clearly states it lists user secret values, with 'my' indicating it's for the authenticated user. Among sibling tools like pc_get_companies_by_company_id_secrets and pc_get_companies_by_company_id_user_secret_definitions, this tool is distinct. However, it could elaborate on what 'user secret values' are.

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 vs alternatives. The description does not mention any prerequisites, restrictions, or comparisons to siblings like pc_get_companies_by_company_id_secrets. The agent is left to infer from nomenclature.

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