tp_get_library_items

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

No annotations provided. Description only states 'List templates implying a read operation, but no behavioral traits are disclosed. Missing information on required permissions, rate limits, or side effects. The burden falls entirely on the description, which is insufficient.

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?

Extremely concise (single sentence), but under-specified. Lacks essential context like return format or parameter usage. The brevity comes at the cost of completeness.

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 tool with 2 parameters, no annotations, and no output schema, the description is incomplete. It does not explain what is returned, how to use the athlete parameter, or the structure of library_id. Essential information is missing.

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 50% (athlete has a description, library_id does not). The description adds no parameter information, such as format of library_id or use of athlete. It fails to compensate for missing schema details.

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?

Description clearly states the tool lists templates in a workout library, using a specific verb and resource. It distinguishes from siblings like tp_get_libraries (list libraries) and tp_get_library_item (get a single item). However, the term 'templates' may be ambiguous as the tool name refers to 'library_items'.

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 versus alternatives like tp_get_libraries or tp_get_library_item. No context about prerequisites, filtering, or scenarios where this tool is preferred.

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