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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the enumerated payload and the `limits` caveat that 'GigNGo runs no background checks,' which is a trust caveat an agent needs when summarizing a worker. It does not cover freshness, caching, or behavior for a nonexistent slug.

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 with no filler, and the purpose plus slug source are front-loaded. The long field enumeration is dense but justified because no output schema exists; only a minor trim would be possible.

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 must carry the return-value burden itself, and it does — names, bio, skills, prices, reviews, filmed-work flag, vouches, badges, service area, availability, URL, and the `limits` object. Slug acquisition and the trust caveat are both covered, leaving nothing an agent needs missing.

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?

Only one parameter with 100% schema coverage, so the baseline is 3; the description goes beyond the schema by explaining slug provenance (search results field or URL pattern), which is real semantic value not present in the schema's example-only description.

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 (Get), resource (public profile of one GigNGo local) and scope (by profile slug), which cleanly separates it from the list-shaped sibling search_local_workers. The scope qualifier 'one ... by their profile slug' makes it unambiguous which tool an agent should pick.

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?

It explicitly says where the required input comes from: 'Slugs come from search_local_workers results (the "slug" field) or from gigngo.org/worker-profile/{slug} URLs,' which routes the agent through the right prior tool. It stops short of stating when NOT to use this tool (e.g. bulk listing) or any exclusion, so it earns a 4 rather than a 5.

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