firestore-delete-document-by-path

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

With no annotations provided, the description carries full burden but only states the deletion action without behavioral details. It doesn't disclose critical traits like permissions required, whether deletion is permanent or reversible, error handling, or rate limits, which are essential for a destructive operation.

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 a single, efficient sentence that front-loads the core action ('Delete a document') and adds necessary qualifiers ('using full path', 'supports subcollections') without any wasted words. Every part earns its place, making it highly concise and well-structured.

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 tool with no annotations and no output schema, the description is inadequate. It lacks information on what happens upon deletion (e.g., return values, confirmation), error cases, or safety considerations, leaving significant gaps for an agent to operate safely and effectively.

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%, so the parameter 'documentPath' is fully documented in the schema. The description adds minimal value by mentioning 'full path' and 'supports subcollections', which aligns with but doesn't significantly expand beyond the schema's example. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Delete') and resource ('document'), and specifies the method ('using full path') which distinguishes it from the sibling 'firestore-delete-document' that likely uses different identification. However, it doesn't explicitly mention Firestore or contrast with all siblings, keeping it from a perfect score.

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 implies usage by mentioning 'full path' and 'supports subcollections', suggesting it's for precise deletion in nested structures. But it lacks explicit guidance on when to choose this over 'firestore-delete-document' or other deletion-related tools, leaving some ambiguity for the agent.

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