bookshelf_get_metadata_schema

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

The annotation readOnlyHint=true already establishes this as a safe read-only operation, so the description doesn't need to cover safety. However, the description adds no additional behavioral context beyond the name—no mention of what the schema contains, whether it returns a list or a single object, or any other operational details. It provides no extra value beyond the annotation and name.

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 a single short sentence with no unnecessary words or fluff. It is efficient, though it sacrifices substance for brevity, which is acceptable given the tool's simplicity.

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?

Given the tool has no parameters, a readOnly annotation, and an output schema, the description is mostly adequate for basic invocation. It clearly states the action and the resource, but it lacks any usage guidance or context to help an agent decide when to use it. This makes it minimally viable but with clear gaps.

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 tool has zero parameters, and the input schema already confirms this. The description is not required to explain parameter behavior, and the baseline of 4 applies since there are no params to describe.

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 'List metadata schema' clearly identifies a specific verb and resource: it lists the metadata schema. However, it does not distinguish this from other schema-related tools, such as bookshelf_get_customformat_schema, leaving some ambiguity about the exact scope of 'metadata 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?

The description provides no guidance on when to use this tool versus alternatives, no context, and no exclusions. It simply states the action without explaining use cases or why one might choose this over other schema-getting tools.

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