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

Beyond the read-only annotations, the description explains how spans are computed, null date behavior, how the parent schedule treats subprojects, that a subproject's own schedule does not move for its parent, and ordering via position. These are substantive behavioral details an agent would not get from annotations alone.

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 dense but well organized, starting with the returned resource and then adding span, schedule, position, and access details. Every sentence contributes, though the scheduling explanation is somewhat heavy for a list tool.

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?

There is no output schema and only one required parameter, so the description carries the return semantics and does so thoroughly. It covers span fields, null handling, parent/child scheduling behavior, ordering, and access, leaving little ambiguity for correct invocation.

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 single projectId parameter is fully described in the schema as the parent project, and the description reinforces that framing. With schema coverage at 100%, this meets the baseline without adding format or edge-case detail beyond the schema.

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 specifically identifies the resource as the projects inserted into a project as subprojects and explains that they are returned in Gantt order with their spans. This clearly distinguishes it from siblings like list_projects, insert_subproject, and get_subtree.

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 implies the tool is for reading a parent project's subproject list and explains access, but it does not explicitly say when to use this versus list_projects, get_subtree, or insert_subproject. Usage is inferable rather than directly guided.

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