delete_project_entry

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

Annotations already indicate destructiveHint=true, so the description adds the claim of 'smart' and 'automatic routing' without explaining what these mean. No details are given about side effects, cascading behavior, or what the routing entails, offering minimal behavioral disclosure beyond the 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 concise (one sentence, 10 words) but lacks key information. It is not front-loaded with the resource or core purpose, sacrificing clarity for brevity. Every sentence should earn its place; this one is too vague to be effective.

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 large set of sibling delete tools and the absence of an output schema, the description is incomplete. It does not explain return values, the effect of the six required parameters (including note fields), or elaborate on the 'automatic routing' claim. The tool's complexity demands more context.

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 100% with all parameters described. The description does not add any additional meaning beyond the schema; it does not explain how parameters influence the 'smart' behavior or routing. Baseline 3 is appropriate as the description adds no value but does not mislead.

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?

Description says 'Smart delete with automatic routing' but fails to explicitly state what resource is being deleted. The resource 'project entry' is only indicated in the tool name and title, which are separate from the description. This vagueness makes it unclear what the tool operates on.

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 over the many sibling delete tools (e.g., delete_file, delete_flow). The description neither states when it is appropriate nor mentions any alternatives, leaving the agent to guess.

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