bookshelf_get_metadata

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

Annotations already declare readOnlyHint=true, and the description's 'fetch' is consistent. However, no additional behavioral context (e.g., error behavior, auth requirements) is provided beyond the annotation, which is acceptable for a simple read operation.

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?

One short sentence contains zero wasted words and is front-loaded with the verb and resource. It is appropriately sized for a simple get-by-id 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?

For a simple tool with output schema and read-only annotation, the description is nearly complete, but it lacks context about what 'metadata' refers to in this system and does not mention the return format or not-found behavior. It is adequate but has room for improvement.

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?

With 0% schema description coverage, the description's 'by id' adds the meaning that the id is the metadata identifier to fetch. This is minimal but sufficient for a single self-explanatory integer parameter.

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 uses a specific verb 'fetch' and resource 'metadata', with 'single' and 'by id' clearly distinguishing it from list_metadata or other get tools. It unambiguously states 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 implies usage via 'single' vs list alternatives, but it does not explicitly state when to choose this over list_metadata or get_metadata_schema. No direct alternative is named, providing only implied guidance.

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