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

Annotations only declare readOnlyHint=false and destructiveHint=false. The description adds real behavioral context beyond that: the idempotency key (composite id address:role:tail), the fact that matching re-posts overwrite the prior profile, and the shape of the returned persisted record. Auth requirements and failure modes on an unpublished scheduleHash remain undisclosed.

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?

Dense but front-loaded: identity and core binding first, then the field list, then return/idempotency semantics. Nearly every clause carries information, though the hex-format repetition of the schema costs some space.

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?

For a 6-param mutation tool with no output schema, the description covers the return value, the composite id, and overwrite behavior. It is close to complete for calling it correctly, missing only permission/validation error behavior and what happens when scheduleHash references an unpublished schedule.

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 documents each field including the role enum and hex formats. The description largely restates the same hex lengths and role provenance, adding only the 'previously published schedule' dependency, so the baseline 3 is appropriate.

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 opens with a specific verb+resource: 'Register a contributor profile binding a wallet address to a role and a published RateSchedule.' That is unambiguous and clearly separable from the sibling pcc_contributor_list, which reads rather than writes.

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?

Usage is implied rather than stated: an agent can infer this is the write path for contributor profiles. The idempotency note ('re-posting the same (address, role, contributorNftTokenId) replaces the prior profile') is genuinely decision-relevant, but there is no explicit when-to-use/when-not or named alternative.

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