Delete Manpower Log

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

Annotations already flag destructive and idempotent behavior, but the description adds crucial details: permanence, repeat calls return 404, and error payload HTTP statuses (401/403/404). This goes well beyond the structured data and is essential for safe invocation.

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 information-dense but not bloated. It front-loads the action, then adds prerequisites, effects, and error handling. The API endpoint line is somewhat redundant but not harmful; each sentence earns its place.

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 two-parameter delete with no output schema, the description is thorough: it covers prerequisites, irreversibility, error responses, default behavior, and the endpoint. An agent has everything needed to invoke the tool safely and correctly.

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 schema already covers both parameters with 100% coverage, so the baseline is 3. The description adds valuable context: project_id defaults to the configured value and id must resolve to an existing parent record. However, the statement that project_id can be omitted when omitted conflicts slightly with the schema marking it required.

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 opens with 'Delete single Manpower Log,' clearly identifying the specific action and resource. It reinforces this with 'Permanently removes the manpower log,' which distinguishes it from sibling list/show/update tools.

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 clear preconditions: confirm the id with the matching show or list tool and resolve the parent record first. It implies this tool is for deletion after discovery, but it does not explicitly name a specific alternative like update_manpower_log or state when not to use it.

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