Retrieve a persisted Statement of Applicability (DdA) with all associated security measures and evidence for ENS compliance assessments.
Obtiene una DdA persistida con todas sus medidas y evidencias.
| Name | Required | Description | Default |
|---|---|---|---|
| record_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true, so the safety profile is covered. The description adds useful context about what is returned (all measures and evidences), but does not explain error behavior, permissions, or what happens if the record is absent.
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 is efficient, though very short, leaving substantial detail to structured fields.
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?
An output schema exists, so return value details need not be in the description, and annotations cover safety. However, the lone parameter is undocumented in both schema and description, and there is no usage guidance, leaving meaningful gaps for an agent.
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 compensate, but it never explains what record_id represents or its format. The only hint comes from the phrase "DdA persistida," which minimally implies an identifier for a specific persisted DdA.
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 states a specific verb ("Obtiene") and resource ("DdA persistida") with an explicit scope of included data ("todas sus medidas y evidencias"). It does not explicitly distinguish itself from the sibling list_dda, but the singular persisted DdA makes the retrieval-by-identifier intent inferable.
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 explicit statement of when to use this tool versus alternatives such as list_dda or get_measure. Usage is only weakly implied by the retrieval verb and the required record_id parameter.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.