get_erskine_may_part

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

No annotations are provided, so the description carries the full behavioral burden. It does convey that this is a read-style retrieval returning a part with title, description and chapter list, but says nothing about authorization, rate limits, error behavior, or pagination. Adequate but thin for a zero-annotation tool.

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 definition is short and front-loads purpose ahead of usage, with Args/Returns sections that are easy to scan. The separate 'Returns' line partially duplicates the earlier 'list of chapters' phrase, which is mild redundancy.

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?

With only one parameter, an output schema present, and no annotations, the description covers purpose, usage context, valid parameter range, and return contents. What is missing is routing detail among the many Erskine May siblings, which it only implies.

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%, so the description must compensate, and it does add the meaningful constraint that part_number is in the range 1-6, which the raw schema does not express. It does not clarify behavior for out-of-range values, keeping it short of a 5.

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 verb and resource ('Get a specific part of Erskine May') and situates it in the document hierarchy ('procedure structure, chapters'). It implicitly distinguishes itself from siblings like get_erskine_may_parts and get_erskine_may_chapter via the hierarchy hint, but it never names those siblings explicitly.

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?

'Use to explore chapters within a part' gives an implied workflow context, but there is no explicit statement of when to prefer this over get_erskine_may_parts or get_erskine_may_chapter, and no exclusions or prerequisites. Usage is inferable rather than spelled out.

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