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

Annotations already establish readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered structurally. The description adds useful context by scoping the returned content (identity, history, contact, tech stack), though it says nothing about response shape or freshness of the data.

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, no filler. The content enumeration is front-loaded and the routing instruction follows immediately, so an agent gets scope and usage priority in a single read.

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 present, the description compensates by enumerating what the overview contains (build focus, founders, location, tenure, contact, technologies), which is exactly what an agent needs to decide whether this tool answers the user's question.

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 per the rubric. There is nothing for the description to disambiguate, and it correctly omits any parameter discussion.

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+resource ('get_company_overview' = who Upforge is) and enumerates the exact facets covered: what they build, founders, location, tenure, contact, and technologies. This clearly distinguishes it from narrower siblings like get_services, get_industries, and get_case_studies.

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 instructs to call this first for general 'who are they / what do they do / are they legitimate' questions, and positions it as the entry point before reaching for more specific tools. That is a concrete when-to-use plus an ordering rule against alternatives.

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