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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds genuine value by disclosing that the response includes recovery state plus an 'app path and next read tool', suggesting a recovery workflow, though it does not explain that behavior further.

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?

A single front-loaded sentence with no filler; the list of returned contents is a bit dense but every clause carries information relevant to selection.

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?

With full annotation coverage, a 100%-documented single parameter, and an output schema covering return values, little is left for the description to carry. The hint about the recovery state and suggested next tool fills the remaining gap adequately for a simple read tool.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents projectId as a UUID. The description never mentions the parameter at all, so it adds nothing beyond the baseline.

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 ('Get details for one BlitzReels project') and scopes it to a single entity, which implicitly separates it from projects_list. It also enumerates what comes back (timeline summary, clips, captions, recovery state), but never names the closest siblings (projects_inspect, projects_list) explicitly.

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: fetch one project by ID when you already have its identifier. There is no when-to-use vs when-not, no mention of alternatives like projects_inspect or projects_list, and no stated prerequisites such as needing a valid UUID.

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