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

Annotations already state readOnlyHint=true/destructiveHint=false, yet the description adds real behavioral context beyond them: a deleted project still returns with isDeleted true, an unknown id returns 'Project not found' rather than erroring, and any project member including viewers can read. Those edge-case and permission facts are exactly what an agent needs and cannot get from 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?

Front-loaded with the payload contents and then the sibling routing, which is the right order. It is a single dense paragraph with many sibling references; every clause carries information, but the density makes it slightly harder to scan than an ideal definition.

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, yet the description enumerates the returned fields, the deleted-project marker, the not-found response, and the permission scope. Combined with the two fully documented parameters, an agent has everything needed to call it and interpret the result.

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% and both parameters already document their provenance (projectId from fastero_list_projects, pythonProjectId from fastero_list_python_projects). The description adds only indirect meaning, noting that entrypoint ids are the values consumed by fastero_run_python_project and fastero_set_python_schedule, but nothing about the two parameters themselves beyond the schema. Baseline 3 is appropriate.

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 ('Read one Python project in full') and then enumerates exactly what is returned: name, description, source, environment, entrypoints, localFiles. It explicitly distinguishes itself from fastero_list_python_projects, fastero_list_python_files and fastero_list_python_runs, so an agent can pick it without opening the schema.

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?

Gives a concrete when-to-use ('to find an entrypoint id or see what is stored') and names the alternative for each neighbor: list_python_projects for the id, list_python_files for folder-by-folder listing, list_python_runs for run history. This is explicit routing, not implied usage.

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