scf_get_evidence_item_maturity

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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description does not need to restate that. It adds some useful behavioral context by listing the returned data dimensions, but it does not disclose additional traits such as auth requirements, rate limits, pagination, or what happens when the evidence item is missing.

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 a single, front-loaded sentence with no wasted words. It states the scope, defines the level scale inline, and lists the output categories compactly. This is an efficient and well-structured description.

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?

With no output schema, the description carries the burden of explaining return values, and it does so by naming current level, contributing factors, upgrade potential, and tracking state. The inputs are fully documented in the schema, and the readOnlyHint covers safety. A small gap is that 'tracking state' and 'upgrade potential' are left terse, and no relationship to the similar evidence-maturity sibling is mentioned, but for a simple read tool this is largely adequate.

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 both parameters already have meaningful descriptions with provenance instructions ('obtain from scf_list_organizations' and 'obtain from scf_list_evidence'). The tool description itself adds no parameter-level semantics beyond what the schema provides, so the baseline score applies.

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 a specific verb-resource pair: 'Get one evidence item's collection maturity', which clearly identifies both the action and the exact scope. It also enumerates what the tool returns (current level on the 1-5 scale, contributing factors, upgrade potential, tracking state), making its purpose unambiguous and distinguishing it from the collection-level sibling scf_get_evidence_maturity via the 'one evidence item' qualifier.

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 clearly implies this tool is for a single evidence item's maturity, giving the agent a straightforward context for when to select it. However, it does not explicitly name alternatives or state when not to use it, such as pointing to scf_get_evidence_maturity for overall maturity or scf_get_evidence_upgrade_recommendations for detailed upgrade paths.

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