oss_capabilities

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses almost nothing: no read-only confirmation, no statement of the response shape or format, and no indication of cost or side effects. The only behavioral hint is that the content is informational (engines, caps), which is inferred rather than stated.

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?

It is a single short clause with no filler, so there is nothing to trim. The brevity is not the problem; the clause is under-specified rather than plainly concise, and the most decision-relevant information (what the tool actually returns or does) is absent.

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 an undocumented required parameter, no output schema, and no annotations, the description should supply return shape and usage context. It supplies neither, leaving the agent to guess what 'unit cap grade' means and how the result should be used.

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 0%, so the description should explain the single project_id parameter, and it does not mention it at all. The bare name project_id is conventionally guessable, which prevents a 1, but the description adds no scoping, format, or required-ness meaning 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 names the subject matter (per-language available engines and unit cap grades), which gives an agent a rough idea of what data comes back. But it is a noun phrase with no verb and no statement of operation, so it never says whether it retrieves, computes, or configures anything. It does not differentiate itself from siblings like oss_units_list or oss_inventory_build.

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 when-to-use statement, no prerequisites, and no reference to any of the ~29 sibling tools. An agent cannot tell from this text whether to call oss_capabilities before building units or whether oss_units_list already covers the same ground.

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