bookshelf_list_metadataprofile

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

The description only restates the resource and operation, adding no behavioral details beyond the readOnlyHint annotation. It does not mention return format, pagination, or any side effects. Since annotations already cover safety, the description contributes no extra context.

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, making it concise and front-loaded. However, it is nearly identical to the tool name, providing minimal added value while still being readable.

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 that this is a simple list operation with no parameters and an output schema exists, the description is minimally viable. However, it lacks context about what a metadataprofile is or when to use this list action versus other related tools, leaving meaningful 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, so the input schema is complete and no parameter documentation is needed. The description correctly implies no arguments are required, meeting the baseline for 0 parameters.

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 clearly states the operation is to list metadataprofiles, using the verb 'List' and the resource. It distinguishes from the sibling 'bookshelf_get_metadataprofile' by implying a plural collection listing. However, it provides no additional scope or context beyond the tool name itself.

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 guidance on when to use this tool versus alternatives such as 'bookshelf_get_metadataprofile' or 'bookshelf_list_metadata'. It does not mention use cases, prerequisites, or situations where one should prefer a different tool.

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