Api organisation objectives destroy

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

Annotations already state destructiveHint=true, idempotentHint=true and openWorldHint=true, and the description adds literally nothing — no statement of what is destroyed, whether cascade deletion occurs, whether permissions are required, or what happens to linked objects. The full burden falls on annotations, and the description contributes zero.

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?

It is short, but that shortness is under-specification rather than conciseness: there is no useful sentence to front-load. The text is an identifier, not prose.

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 destructive mutation with no output schema and no documented parameters, the description should at minimum describe the target resource, deletion semantics, and id expectations. None of that is present.

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 0% for the single required 'id' parameter, so the description must compensate — yet it says nothing about what the id identifies or its format. Compare this to the 0-parameter baseline of 4, which does not apply here because there is one undocumented parameter.

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 is the raw operation identifier repeated verbatim ('api_organisation_objectives_destroy'), which only tautologically restates the name and title. It does implicitly encode a verb (destroy) and a resource (organisation objectives), so it isn't entirely meaningless, but it offers no sanctioned-language statement of what the tool does and nothing to separate it from siblings like organisation_objectives_update or organisation_objectives_partial_update.

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?

There is no guidance on when to delete an objective versus updating, deactivating (is_active endpoints exist), or duplicating it, and no stated prerequisites. The agent receives no information about alternatives or exclusions.

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