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

With no annotations, the description carries the full behavioral burden. It discloses a non-obvious resolution chain (street → saved profile → GitHub → sample) which is useful, but it omits safety characteristics (read-only), doesn't clarify what 'on the street' means, and mentions 'preview:true' even though no such parameter exists in the schema, causing confusion.

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 purpose is front-loaded in the first sentence, and the fallback behavior follows compactly in the second. There is no filler, though the second sentence is dense and relies on domain jargon ('on the street') that is not explained.

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?

The description covers what the profile contains and the fallback resolution order, which is appropriate for a 5-parameter tool. However, it leaves important context implicit: the relationship to siblings, the meaning of 'street', and the mismatch between 'preview:true' and the actual mode parameter. With no annotations and no output schema, more behavioral clarity would help.

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%, so the schema already fully documents all five parameters, including enums for lang and mode. The description adds no parameter-level meaning beyond what the schema provides, and the mention of 'preview:true' does not map to any listed parameter.

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 names the resource (developer/company profile) and enumerates the content it returns (bio, links, badges, projects, contributions). It is distinguishable from siblings like get_project or get_building, but it doesn't explicitly contrast itself with them.

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 describes the internal lookup fallback but offers no guidance on when an agent should call get_profile versus alternatives like about, search, or get_project. There are no explicit when-to-use or when-not-to-use statements.

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