Delete a goal

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

The description adds the authorization class ('board_or_agent') and the exact API path, which go beyond the annotations (destructiveHint=true, etc.). It correctly identifies the operation as a DELETE. No contradiction with annotations.

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 very brief (two sentences), but it repeats the title in the first sentence. It is concise but could be more structured by front-loading the key info without 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?

Given it is a destructive operation, the description lacks warnings about irreversibility or side effects. There is no mention of return values despite an output schema existing. The auth info is helpful, but overall context is insufficient for a delete tool.

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 description does not explain any parameters. The input schema has 50% coverage (description for 'body' exists, but 'path.id' lacks explanation). The description adds no meaning to the parameters, leaving the agent to rely solely on the schema.

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 first sentence explicitly state 'Delete a goal', and the HTTP method 'DELETE' clarifies the action. However, it does not explicitly differentiate from sibling goal tools (e.g., pc_patch_goals_by_id) beyond the verb, so it's clear but not fully distinguishing.

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 is provided on when to use this tool versus alternatives like pc_patch_goals_by_id or pc_post_companies_by_company_id_goals. There is no mention of prerequisites or contexts where deletion is appropriate.

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