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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds a cost note ('Free') and a fidelity guarantee ('Preserve project, clip and edit metadata exactly'), which is modest extra context beyond the annotations but not rich behavior disclosure.

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?

Three short, front-loaded segments: the action, the fidelity guarantee, and the cost/no-side-effect note. Zero filler and the key identifying verb+resource leads.

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 single-parameter read tool whose annotations already declare the safety profile, the description covers identity, scope and side-effect behavior. No output schema exists, but a 'read one' tool's return shape is implied; completeness is adequate though it says nothing about permissions or missing-project behavior.

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?

One parameter with 0% schema description coverage. The schema itself carries the uuid format and pattern, and the description only echoes that lookup is 'by projectId' without adding format, validity or sourcing semantics. It neither compensates for the coverage gap nor is it needed for a single self-describing identifier.

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 ('Read one atomic editor project by projectId') with clear scope ('one', keyed by projectId), which distinguishes it from batch/list siblings. It does not explicitly name how it differs from soclo_editor_discover, soclo_editor_edit or soclo_editor_schema, so it stops short of full sibling differentiation.

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?

The description gives no when-to-use or when-not guidance and names no alternatives. An agent cannot tell from this text why it should call soclo_editor_read rather than soclo_editor_discover or soclo_editor_schema for a given project.

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