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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: ordering (newest first), exclusion of deleted items, the returned field set, and the fact that the _id maps to pythonProjectId used by other Python tools.

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?

Front-loaded with the core action and heavily information-dense with no filler sentences. The single long sentence is slightly run-on and packs clauses together, but every clause (ordering, exclusion, returned fields, sibling disambiguation) 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?

There is no output schema, so the description correctly carries the burden of describing return values (_id, name, source, environment, entrypoints, runnable files by id). Combined with the annotations covering the read-only profile, an agent has everything needed to call it 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?

Schema description coverage is 100% and projectId is fully documented in the schema ('The project's id, from fastero_list_projects'), so the baseline of 3 applies. The description adds no additional parameter syntax, format, or edge-case behavior for projectId.

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 ('List a project's Python projects (script workspaces)') and immediately differentiates itself from fastero_list_python_files by scope (projects vs. files). An agent can distinguish it from fastero_get_python_project and fastero_list_projects without opening schemas.

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?

Names the alternative sibling (fastero_list_python_files) and its distinct scope, plus the project-scoping requirement via projectId. It lacks explicit 'when not to use' guidance versus fastero_get_python_project for single-project lookups, but the context is clear.

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