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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the returned node shape (id, name, description, children), the handsOff flag and its inheritance to descendants, and the constraint that hands-off features cannot be changed.

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?

Roughly four sentences, front-loaded with purpose before return shape and parameters. Every sentence carries information, though the featureId sentence partially duplicates the schema and the revision note is slightly detached from the listed return fields.

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, the description correctly takes on the burden of describing the returned tree, including the root and the handsOff inheritance rule. It also notes the cross-tool revision dependency. Minor gap: it never states where 'revision' lives in the response, given the field list omitted it.

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 both parameters are already documented, including featureId's 'read only this feature and the features under it'. The description restates that scoping behavior almost verbatim and adds no format, id-source, or default guidance, 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?

States a specific verb and resource ('Get a project's features') and immediately narrows the shape with 'as a compact tree', plus names the sibling that consumes the result (update_features). An agent can distinguish this from get_project or list_projects without opening any schema.

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?

Gives clear context: use the default call for the whole project tree, or 'Pass featureId to read just that feature and the features under it.' It also flags the downstream dependency ('update_features needs the returned revision'), which tells the agent when this call is a prerequisite. No explicit when-not-to-use exclusion, so it falls short of a 5.

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