scf_get_evidence_item_maturity

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

With no annotations, the description carries full burden. It states 'Get' implying read-only and lists returned fields, giving a good overview. However, it does not disclose permission requirements, idempotency, or side effects beyond the obvious read operation.

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 sentence that efficiently communicates the tool's purpose and return value components. It is front-loaded and contains no extraneous information.

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?

Without an output schema, the description is the sole source for understanding return values. It lists four components, which is reasonably complete for a getter tool. However, it does not clarify how this tool differs from similar siblings, leaving the agent to guess the precise scope.

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% with both parameters already documented with guidance (org_id from scf_list_organizations, evidence_id from scf_list_evidence). The tool description adds no additional parameter semantics, so baseline score of 3 is appropriate.

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?

Description clearly states it gets one evidence item's collection maturity, listing the specific components returned (current level, contributing factors, upgrade potential, tracking state). This distinguishes it from siblings like scf_get_evidence_maturity (likely only level) and scf_get_evidence_upgrade_recommendations (focus on upgrade potential).

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 by listing what the tool returns, but provides no explicit guidance on when to choose this tool over alternatives. The agent must infer usage from the description alone.

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