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

Beyond the readOnly/idempotent annotations, the description adds meaningful behavioral context: outcome basis is either 'measured' or client-reported with attribution, and estimates are never included. This helps the agent calibrate trust in the returned data, which is not inferable from annotations alone.

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?

The description is compact and front-loaded with the most important fact: real client projects with outcomes. Every sentence earns its place, including the evidence-basis caveat and the explicit exclusion of estimates. No filler or repetition.

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?

With no output schema, the description carries the burden of explaining what the agent will get, and it does so thoroughly: outcomes, what was built, live-site link, and the trustworthiness basis of each outcome. The two optional parameters are already fully documented in the schema, so nothing essential is missing for correct invocation.

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 input schema already covers both parameters with 100% description coverage: limit has range/default details and category is explained as an optional filter. The tool description adds no extra parameter-level meaning, so the baseline score of 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?

The description clearly identifies the resource as 'Real Upforge client projects' with their outcomes, built items, and live-site links. This distinguishes it from sibling tools like get_services and get_industries by emphasizing portfolio proof rather than offerings or industry categories.

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?

The description explicitly states when to use it: for queries like 'show me their work', 'do they have proof', or 'have they built anything like mine'. It gives strong contextual guidance but does not explicitly name alternatives or state when not to use it, so it falls just short of the top tier.

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