read_collection

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'GET' is consistent. It adds one useful behavior beyond annotations: 'fully paged' (automatic pagination), but it doesn't explain return shape, truncation behavior (covered for limit in the schema), or rate limits. With annotations as baseline, it adds a bit but not rich context.

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 entire description is one sentence: the verb and target are front-loaded, examples are compact, and the reference to read_meta is a purposeful pointer. No filler or repeated schema content.

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 10-parameter tool, the schema covers most parameters and annotations cover the read-only/open-world safety profile. The description supplies the missing path pattern and pagination behavior, and points to read_meta for vocabulary. The main gaps are the unexplained 'layer 1' term and the absence of output-shape guidance, but these are not fatal given schema richness.

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 coverage is 90%, so the schema handles most parameter documentation. The description adds value by showing how resource, id, and collection combine into a path, and by telling the agent to consult read_meta for valid collection names. This is modest but real meaning beyond the schema fields.

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 opens with 'GET an inner collection of an entity' and gives concrete path examples (UserStories/{id}/Tasks, Bugs/{id}/Comments), so the operation and resource are clear. It distinguishes itself from read_meta by pointing there for collection names, but it doesn't explicitly differentiate from other read_* siblings such as read_comments or read_get.

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 usage context: you use it when you need a nested collection of an entity, and it directs the agent to read_meta for valid collection names. It does not state when not to use it or name alternative tools for top-level reads/search, so guidance is implied rather than explicit.

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