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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description adds useful non-annotation context: it returns a single object and requires 'the user's Cotlet API key with access to this app,' which is genuinely important setup information. It stops short of noting any rate limits or failure modes.

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 resource and its scope, and the workflow guidance follows logically. There is mild redundancy: the opening sentence and the 'Returns one project...' sentence restate the same budget/skills/proposals content, which could be tightened.

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 one-parameter read tool with no output schema, the description explains what the return contains (brief, budget, skills, proposal count) and the auth prerequisite, which is sufficient. Absence of output schema is offset by enumerating returned fields.

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 the sole parameter (project_id) is documented in the schema as 'Project ID from search_projects.' The description adds no syntax or format detail beyond that, so the schema carries the load; a baseline 3 is correct.

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/fetch one project) and enumerates the scope of what it returns: full brief, budget, required skills, and proposal count. It clearly reads as a single-item retrieval distinct from siblings like search_projects (listing) and send_proposal (action). An agent can tell what it does 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?

Explicitly recommends using it before send_proposal and explains why: 'so your agent reads the brief instead of the title.' That is a clear usage condition tied to a named alternative. It does not state exclusions (e.g., use search_projects first to obtain the ID), though the parameter description implies that flow.

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