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

With no annotations, the description carries the full behavioral burden, and it discloses only one trait: private projects yield nothing. It does not say whether that means an empty result versus an error, what the returned project object contains, or whether any auth/visibility rules apply.

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, zero waste, and the private-project caveat is stated up front. But the brevity tips into under-specification: the lead sentence is a fragment rather than a front-loaded statement of action and result.

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 six-parameter read tool with no annotations and no output schema, the agent needs to know what a project object looks like and how it differs from a profile. The description covers neither, and it never touches the mode/seed context that shapes non-default modes.

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 83%, so the schema already documents lang, mode, seed, github, and project; the description adds no further meaning. Notably, 'handle' has no schema description and the description does nothing to explain it or its relation to 'project'.

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 identifies the resource ('a single project of a profile') but is a noun fragment with no verb, so the agent must infer retrieval from the tool name. It implicitly contrasts with list_projects by saying 'a single project', but never names that sibling or states the operation 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?

'Returns nothing for private projects' is a caveat about outcomes, not a when-to-use rule; there is no guidance on when to call this versus list_projects, get_profile, or preview_building. The agent gets no exclusion criteria or prerequisites.

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