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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations by listing the exact fields returned, including the `limits` field and the notable fact that GigNGo runs no background checks.

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 dense sentences with no filler. The core action and resource are front-loaded, the return contents are listed compactly, and the slug-sourcing guidance earns its place.

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?

Complete for a simple read-by-slug tool. With one required parameter, no output schema, and a thorough enumeration of return fields plus notes on data provenance and limitations, an agent has enough context to invoke this tool correctly.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining where a valid slug comes from: the 'slug' field on search_local_workers results or a gigngo.org/worker-profile/{slug} URL, which helps agents source the parameter correctly.

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 the public profile of one GigNGo local by their profile slug.' It clearly enumerates what the profile contains and is naturally distinguished from sibling tools like search_local_workers, which finds locals rather than reading one profile.

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?

Implies clear usage context: call this tool when you already have a slug, which can come from search_local_workers results or from a gigngo.org profile URL. It does not explicitly list when-not-to-use or alternatives, but the workflow prerequisite is stated clearly enough for an agent to choose correctly.

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