octri_list_sdk_repos

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

No annotations are provided, so the description bears the full behavioral burden, yet it says nothing about read-only semantics, ordering, completeness of the list, pagination, or what happens when a project has no SDKs. The only added context is that repos are grouped per language and linked to SDKs.

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?

A single short fragment with no padding, and the key qualifier ('linked to the project's SDKs') is front-loaded. It is arguably under-specified rather than truly economical, but nothing is wasted.

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 simple one-parameter read tool with full schema coverage and no output schema, the description covers the essential what. However, with no annotations and no output schema, it should at least confirm this is a read-only listing and sketch the return shape, which it does not.

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 100% and the single optional parameter's fallback behavior is documented in the schema itself, so the baseline is 3. The description's phrase 'linked to the project's SDKs' hints at project scoping but adds no syntax or format 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 fragment names a specific resource — per-language GitHub repositories tied to the project's SDKs — which goes beyond restating the tool name and lets an agent distinguish it from siblings like octri_list_specs or octri_list_languages. It lacks an explicit verb, but the 'list' prefix plus the precise resource scope makes the intent clear.

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?

There is no statement of when to reach for this tool versus octri_list_generated_files, octri_fetch_artifacts, or other SDK-facing list tools, and no mention of prerequisites or the fallback-to-selected-project behavior beyond what the schema already says. Usage must be inferred entirely from the name.

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