bookshelf_get_system_task

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

The annotation readOnlyHint=true is consistent with the description's 'List' operation, so there is no contradiction. However, the description adds no extra behavioral context beyond the annotation—no mention of pagination, response scope, or any constraints. It does not add value beyond what annotations already provide.

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 very short and to the point, but it is a fragment ('List system task') rather than a complete sentence. It is not verbose, but it lacks structure and fails to capitalize on the chance to provide minimal useful context. It is appropriately concise but under-specified.

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 tool has no parameters and an output schema exists, the description's job is minimal. However, it still doesn't clarify what 'system task' refers to or indicate whether it lists all system tasks. It is adequate for a simple list operation but leaves the agent to infer too much from the name.

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 input schema has zero parameters, so schema description coverage is 100% vacuously. The description does not need to compensate for parameter documentation. Baseline for no parameters is 4, and the description adds nothing harmful or missing.

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 uses a clear verb 'List' and a resource 'system task'. It distinguishes from the sibling 'bookshelf_get_system_task_by_id', which implies getting a specific task by ID, while this lists tasks. However, it does not explicitly state scope like 'all' or 'system tasks', so it could be slightly clearer.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of when to use 'list' vs 'get by id' or any context about filtering or prerequisites. It is a bare statement without usage context.

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