bookshelf_get_config_mediamanagement

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

Annotations already indicate readOnlyHint=true. The description only adds 'List', which is consistent but provides no additional behavioral context (e.g., what the listing entails, potential exceptions, or format).

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 fluff. It is minimal but adequate for a zero-parameter read operation; however, it borders on under-specification.

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 low complexity, output schema presence, and read-only annotation, the description is workable. Yet there is ambiguity about whether it returns a list or a single object, and the meaning of 'config mediamanagement' is not expanded on.

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 description has no need to explain them. The input schema is empty and schema coverage is 100%, meeting the baseline for no-parameter tool.

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 config mediamanagement' uses a specific verb 'List' and a resource 'config mediamanagement'. It distinguishes from siblings like get_config_mediamanagement_by_id and update_config_mediamanagement, though it lacks 'all' or explicit scope.

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?

No guidance on when to use this tool vs alternatives. It does not mention any conditions, exclusions, or didactic advice on what to do with the result.

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