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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds significant behavioral context beyond them: non-owners receive a deliberate 404 indistinguishable from a missing tool, there is no visibility parameter, the body is the most private member data stored, and reading is separate from running. This is exactly the kind of non-obvious behavior an agent needs to reason correctly.

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 longer than a typical get operation, but each sentence carries meaningful operational guidance: the 404 ambiguity, the privacy rationale, the separation of read vs execute, and the ordering instruction. It is front-loaded with the core purpose. It loses one point because some phrasing is redundant and could be tightened without losing information.

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 operation with no output schema, the description provides everything an agent needs: what the record contains, how to obtain the id, the ownership restriction, the deliberately misleading 404, and the recommended call order relative to synthetic_tool.execute. Nothing critical is missing.

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?

The schema already covers the single `id` parameter at 100% and explains it is a `syn_…` id from synthetic_tool.list. The description adds little new meaning about what the parameter is, instead focusing on auth and 404 semantics. Per the baseline rule for high schema coverage, a 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 and resource: 'Read one synthetic tool', and states exactly what the read returns (the input_schema, the steps it runs, and the record directly). It also implicitly distinguishes itself from synthetic_tool.list by saying 'one' tool, and from synthetic_tool.execute by noting that reading is not permission to run. This leaves no ambiguity about what the tool does.

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 explicit guidance on when to call this tool: 'Read this before synthetic_tool.execute — the input schema is author-defined and cannot be guessed.' It also tells the agent when not to treat results as expected by explaining the ownership 404 behavior and that reading does not grant execution rights. This is strong routing guidance relative to its siblings.

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