get_library_sections_by_section_id_common

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

The description adds no behavioral detail beyond what the annotations already provide: readOnlyHint, idempotentHint, and destructiveHint=false. The endpoint line restates the method as GET, which the annotations already imply, and there is no mention of auth requirements, response behavior, or other operational details.

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 compact and front-loaded with the core action, followed by the endpoint and argument list. There is no wasted text, though the brevity contributes to the lack of context.

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 read-only annotations and presence of an output schema reduce the burden on the description. However, the phrase 'common fields for items' is vague and the description does not clarify what 'common' means or how this endpoint relates to the many similar sibling endpoints, leaving some ambiguity for an agent trying to decide whether it is the right tool.

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?

Schema description coverage is 0%, and the description gives one line: 'section_id: Section identifier'. This is minimally helpful but mostly restates the schema's property title 'Section Id' and does not explain how the section_id maps to the path or where to obtain it. With only one required parameter, it is just barely adequate.

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 specific action and resource: 'Get common fields for items' plus the concrete endpoint 'GET /library/sections/{sectionId}/common'. This is clear enough, though it does not differentiate itself from the many sibling get_library_sections_by_section_id_* tools.

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 the many similar section-related endpoints such as get_library_sections_by_section_id_categories or get_library_sections_by_section_id_albums. No exclusions, alternatives, or context are provided.

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