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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered without description help. The description adds the content scope of the lookup but says nothing about auth requirements, rate limits, or what happens if the login is unknown; with annotations carrying safety, this is adequate but not rich.

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 core identity ('Who is this person... by GitHub login') is front-loaded, and the following enumeration of returned fields plus the usage sentence are all informative rather than filler. The middle sentence is a dense run-on list, which costs a little readability, but nothing is wasted.

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?

There is no output schema, so the description carries the burden of conveying return contents — and it does so thoroughly by enumerating the facets. Combined with the stated use case and the annotation-covered safety profile, an agent has enough to call it correctly; only lookup-failure and auth behavior remain unaddressed.

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% — the login parameter is documented in the schema with format constraints and examples. The description only restates 'by GitHub login' and adds no format, case-sensitivity, or lookup-failure semantics, so baseline 3 is correct.

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 states a specific verb and resource ('who is this person in the Canton Dev Fund, by GitHub login') and enumerates the distinct data facets returned: SIG memberships, authored proposals, review/comment activity, review requests, assignments, and champion lines. That granularity clearly distinguishes it from siblings like search_dev_fund, get_dev_fund_activity, and find_expert.

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 gives an explicit use case: 'Use to judge who a possible champion or reviewer is and how responsive they are.' That tells the agent when this tool is relevant, but it names no alternatives (e.g. find_expert or list_proposals_needing_champion) or explicit exclusion conditions, so it falls short of a full 5.

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