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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety behavior is covered. The description adds meaningful behavioral context beyond annotations: it distinguishes 'not read' from 'not a proxy', explains that selector signature candidates are guesses and never names, and separates creation calls from other calls. It does not cover auth, rate limits, or response format, but it adds substantial interpretation guidance.

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 description is an extremely long, dense paragraph that front-loads returned field details instead of the tool action. Key invocation guidance is buried at the end, and the structure is difficult to parse. It is over-specified for a concise tool definition rather than appropriately sized.

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 and only sparse annotations, the description carries the burden of explaining return values, which it does in extensive field-level detail. It covers contract identity, verification metadata, proxy history, interface changes, and activity counts. It is still unstructured and omits some edge cases, but it is complete enough for an agent to understand the data shape.

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 67%, and the address parameter has no schema description. The description compensates by explaining that chainId plus address selects one contract, while slug returns all contracts for a project. This clarifies the intended parameter combinations and adds meaning beyond the schema, though it does not address what happens when no required parameters are supplied.

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 identifies the resource (a contract as a research entity) and says it can be fetched by chainId/address or project slug, but it never states a clear retrieval verb up front. Most of the text enumerates returned fields rather than what the tool does, and it does not differentiate itself from sibling tools. An agent can infer the purpose, but it is buried and vague.

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 explicit parameter combinations: chainId and address for one contract, or slug for every contract in a project. That is useful invocation guidance, but there is no when-to-use context, no exclusion criteria, and no routing to sibling tools such as get_project_coverage or get_project_snapshot. Usage is implied rather than fully specified.

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