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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false), but the description adds valuable behavioral context: it explains the return shape, tells the agent to pass `id` as `projectId`, and describes the locationCode/languageCode fallback semantics. These are non-obvious behaviors beyond the structured fields.

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?

Every sentence earns its place: purpose, usage trigger, return mapping, and fallback semantics are all front-loaded and directly actionable. No repetitive or filler content.

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 simple zero-argument read operation with annotations and an output schema, the description is complete enough to call correctly. It explains how to consume the result and why the project metadata matters, so no further guidance is required.

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?

The tool takes zero parameters, so the baseline is 4. The description implies there are no filters or arguments by saying it lists all organization projects, which is adequate for this simple no-argument lookup.

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 ('Lists all projects') with clear scope ('in the user's organization'). It is distinguishable from siblings like create_project and delete_project without opening any 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?

Explicitly says when to use it: 'whenever you need a `projectId` for another HarborRank tool.' That is a precise trigger condition for an agent, and there is no competing sibling that lists projects.

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