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

Annotations already flag destructiveHint=true, yet the description goes well beyond that by enumerating exact consequences: the project leaves fastero_list_python_projects, schedules are switched off, it can no longer be run/scheduled/written to. It also clearly separates irreversibly erased stored files from preserved run history, which is precisely the kind of detail an agent needs for a destructive call.

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?

Two sentences, front-loaded with the action and scope, then the consequences in a single dense clause. No filler or repetition of the title.

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 two-parameter tool with no output schema, everything needed to call it safely is present: scope, listed consequences, what is retained versus destroyed, and unrecoverability. No relevant gap remains.

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 100% and both parameters already document their source (fastero_list_projects, fastero_list_python_projects). The description adds no additional meaning about the identifiers, so the baseline 3 applies.

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?

States a specific verb and resource ("Delete a Python project") plus the blast radius ("for everyone in the project"), which is far stronger than the bare title. It doesn't explicitly contrast with sibling delete tools (delete_notebook, delete_streamlit_app), but the resource naming makes selection unambiguous.

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?

Usage is implied by the operation type, but there is no explicit when/when-not guidance, e.g., that disabling schedules or triggers (set_schedule_enabled / disable_trigger) is the non-destructive alternative, or that a project that must remain runnable should not be deleted. The agent must infer the trade-off.

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