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

The annotations already declare this as a non-destructive, read-only, closed-world operation. The description adds useful context that it returns the currently active version, but it does not address permissions, failure behavior, or how the lookup resolves across the optional id/ref/company parameters.

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?

It is a single front-loaded sentence with no filler or repetition. Every part of the sentence contributes to the stated operation.

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?

The description is adequate for a read-only single-record retrieval with an output schema and safety annotations. However, for a nested input schema with three optional identifier-related parameters, it does not clarify how to select a schema definition or distinguish this tool from adjacent schema-version and resolve tools.

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 has moderate description coverage (67%) and defines the id, ref, and companyId shapes, but the description adds no parameter-level semantics. It does not explain when to use id versus ref or how companyId constrains the lookup, leaving the schema to carry most of the burden.

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 states a clear verb and resource: read one schema definition plus its currently active version. It distinguishes itself from list-oriented siblings by specifying 'one', but it does not explicitly differentiate itself from close siblings such as schema_get_schema_version or schema_resolve_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?

There is no explicit guidance on when to use this tool versus schema_get_schema_version, schema_resolve_schema, or the list variants. The only usage signal is the implied single-record retrieval, which is not enough to guide an agent among similar schema tools.

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