sx_get_app_parameter

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It only states the action of 'getting' a parameter, without mentioning read-only nature, authentication requirements, or side effects. This is insufficient for an agent to understand the tool's behavior.

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 short sentence, which is concise and front-loaded. However, it lacks necessary detail to be considered appropriately sized for the tool's purpose, making it under-specified. A 3 reflects adequate conciseness but insufficient completeness.

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 and no annotations, the description should provide more context about what the parameter is, what it returns, and typical use cases. It does not, so the agent lacks essential information to use the tool correctly. Score 2.

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%, and the description offers no explanation of the two parameters, app_code and para_code. The mention of operation.loadAppParameter does not clarify parameter meanings. This is a significant gap.

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 it gets a 'three-effect system parameter' but the term is ambiguous and not defined. It does not distinguish from sibling tools or specify the resource type beyond 'parameter'. This is vague rather than a tautology, hence a 3.

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?

No guidance is given on when to use this tool versus the many sibling tools (e.g., sx_get_by_id, sx_list_query). The description does not provide context or exclusions, leaving the agent to infer applicability. Score 2.

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